# Pr Feedback

> Address reviewer feedback on an existing open GitHub PR — fetch every review comment and thread, group them into a numbered accept / pushback / needs-discussion list, wait for the user's approval, apply the accepted fixes, ship through /commit-push-pr on the same branch, and reply to each addressed thread citing the fixing commit SHA. Use when the user says \"address the review comments\", \"hand…

- **Type:** Skill
- **Install:** `agentstack add skill-devarfeen-agent-skills-kit-pr-feedback`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [devarfeen](https://agentstack.voostack.com/s/devarfeen)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [devarfeen](https://github.com/devarfeen)
- **Source:** https://github.com/devarfeen/agent-skills-kit/tree/main/skills/pr-feedback

## Install

```sh
agentstack add skill-devarfeen-agent-skills-kit-pr-feedback
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# pr-feedback

One iteration of working reviewer feedback on an open PR, ending in pushed fix commits and a reply on every settled thread. The boundary against its neighbours: /code-review produces a review, this skill consumes one; /commit-push-pr opens or updates the PR, this skill never creates one.

## Inputs

- **The PR** — a number or URL from the user, else detected from the current branch: `gh pr list --head "$(git branch --show-current)" --state open --json number,title,url`. No open PR found (or more than one) → stop and ask which PR this is; never guess and never create one.
- **The head branch checked out** — fixes land on the PR's head branch. If the checkout is elsewhere, switch to it; if the working tree holds unrelated uncommitted changes, stop and ask before touching anything.
- **`gh` authenticated** — if `gh auth status` fails, stop and report.

## Rules

- **One combined approval gates every remote write.** Present the feedback list — planned fixes, pushback replies, wontfix candidates — and wait; until the user approves, everything stays a local draft: no fix commit, no push, no reply, no thread resolution.
- **Reply to or resolve only settled threads.** A thread earns a reply when its fix is in a pushed commit, or when the user explicitly approved answering it as a wontfix; every other thread stays open and unanswered — an unearned "done" reply misleads the reviewer.
- **Pushback and needs-discussion items go to the user.** Never silently apply a fix you would push back on, and never silently drop one; both classifications exist to force a human decision.
- **Fixes stay inside the comment's boundary.** A "small review fix" that grows behavioural scope — new states, changed interfaces, changed data shapes — is a stop signal: park the item, tell the user, and route it to /to-tickets as its own slice.
- **Never force-push.** The PR's commit history is the review record; ship new commits on the same branch and let /commit-push-pr update the existing PR.
- **Zero attribution.** No co-author, AI, or tool attribution in commit messages, thread replies, or PR edits — scrub tool-injected trailers before anything is written remotely.
- Emit `Stage / Found / Next / Needs user` at each phase transition — one line per field.

## Workflow

### 1. Locate the PR

Resolve per Inputs, then read it: `gh pr view  --json number,title,url,state,headRefName,baseRefName`. State not `OPEN` → stop and report; feedback on a merged or closed PR needs the user's call. Record the pre-run remote head for the completion check: `git rev-parse origin/`.

### 2. Fetch every thread

Review threads — with thread IDs and resolved state — exist only in GraphQL:

```bash
gh api graphql -f query='query { repository(owner:"", name:"") {
  pullRequest(number:) { reviewThreads(first:100) {
    pageInfo { hasNextPage endCursor }
    nodes {
    id isResolved isOutdated path line
    comments(first:50) { nodes { databaseId author { login } body } } } } } } }'
```

Re-query with `after: ` until `hasNextPage` is false — same idea for any thread whose comments exceed the first 50.

Also collect top-level review bodies and issue-style PR comments (`gh pr view  --json reviews,comments`) — reviewers often put the substantive ask there. Skip threads already resolved.

### 3. Classify into a numbered list

One line per comment, one classification each:

- **accept** — the comment is right and bounded; note the planned fix in a few words.
- **pushback** — you disagree; note why in one clause and draft the reply you would post.
- **needs-discussion** — the right answer depends on information only the user or reviewer has; note the open question.

Emit the list in the Output template and stop.

### 4. Get the user's decisions

Wait for the combined approval. The user may reclassify: an overruled pushback becomes an accept; a vetoed accept becomes a user-approved wontfix (reply drafted, no code change). One question at a time, leading with the recommended answer so the user can accept it in a word. Record the final per-item disposition; it drives every later step.

### 5. Apply the accepted fixes

Work through the accepted items on the head branch — the smallest change that answers each comment — and run the tests the touched code has: name the command, quote its passing tail, and open the PR's how-to-test plan with it. Failures that persist with the fixes stashed are pre-existing — record them in the final report (step 8) and continue; failures the fixes introduced stop the item. No tests cover the touched code → say so in the final report. An item that hits the scope-creep stop signal gets parked as needs-discussion; keep going on the rest.

### 6. Ship through /commit-push-pr

Invoke /commit-push-pr on the same branch — it detects the existing PR (`gh pr list --head`) and updates it instead of opening a duplicate. Capture the commit SHA(s) it reports.

### 7. Answer the threads

Only now, and only for settled items:

- Fixed items: reply on the thread citing the SHA — `gh api repos///pulls//comments//replies -f body='Fixed in  — .'`
- User-approved wontfix or pushback: post the approved reply; leave the thread unresolved so the reviewer gets the last word.
- Resolve a thread (GraphQL `resolveReviewThread`) only when its fix commit is pushed and its reply posted.
- Settled non-thread items — top-level review bodies and issue-style comments from step 2: answer with `gh pr comment  --body 'Fixed in  — .'`
- needs-discussion items: no reply unless the user supplied one — report them as still open.

### 8. Report

Per Output: the final report line, a second line for any step-5 record, then the footer.

## Output

Feedback list (step 3), one line per comment:

```
PR # —  ( unresolved threads)
1. [accept] src/auth/session.ts:42 — @reviewer: token TTL hardcoded → read from config
2. [pushback] src/api/routes.ts:88 — @reviewer: split this handler → cohesive as-is; draft reply attached
3. [needs-discussion] review body — @reviewer: should errors retry? → depends on queue semantics, your call
Decisions needed on 2–3. Nothing is committed, pushed, or replied to yet.
```

Thread replies: 1–2 sentences, citing the fixing commit SHA.

Final report, one line: `PR #:  fixed and replied (),  replied wontfix,  still open for discussion`; a second line carries any step-5 record.

Then `Suggested next skills (optional)` — 1–3 advisory items (e.g. /code-review to self-review the fix commits), never gating.

## Completion criteria

- [ ] Threads re-fetched after replying: every accepted item's thread carries a reply citing a SHA that `git branch -r --contains ` places on the PR's head branch
- [ ] No thread replied to or resolved whose disposition was not fixed-and-pushed or user-approved wontfix — checked against the step 4 disposition list
- [ ] `git merge-base --is-ancestor  origin/` succeeds, where `` is the pre-run remote head from step 1 — history only grew, no rewritten SHAs
- [ ] Pushed commits, replies, and PR edits read back with no attribution text
- [ ] Final report line printed and the `Suggested next skills (optional)` footer appended

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [devarfeen](https://github.com/devarfeen)
- **Source:** [devarfeen/agent-skills-kit](https://github.com/devarfeen/agent-skills-kit)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-devarfeen-agent-skills-kit-pr-feedback
- Seller: https://agentstack.voostack.com/s/devarfeen
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.