Fix PR
Flags
| Flag | Effect |
|---|
| Target PR. Default: on current branch; stop and ask if none. |
| Commit locally; skip push. Off by default. |
| Fix code; skip GitHub thread replies. Off by default. |
Step 1: Resolve PR
if passed; else
gh pr view --json number,headRefName,url,headRepository
.
Record owner, repo, number, head branch, URL. If
errors or no PR exists,
stop and ask.
Done when: owner, repo, number, head branch, and URL are known.
Step 2: Fetch open feedback
Paginate all unresolved review threads using the GraphQL contract in
. Substitute owner, repo, and number from Step 1.
If a changes-requested review has a body with actionable feedback not already
covered by inline threads, add those items using the REST pattern in
.
Done when: Every unresolved thread and orphan review-body item is listed with
path, line, author, and body.
Step 3: Checkout PR branch
or confirm the working tree is on
.
Done when: Working tree is on the PR head branch.
Step 4: Triage skeptically
For every item from Step 2. No file edits until this step completes.
- Read the cited file with surrounding context.
- Trace the code path the reviewer claims is wrong.
- Reproduce if possible (targeted test, call trace, type check).
- Assign verdict: | | .
- Record one-line evidence.
Done when: Every item has verdict and evidence; no edits before this holds.
Step 5: Implement
Apply only
verdicts. Focused diffs; no drive-by refactors.
Done when: Every
item has a local change, or there were zero
verdicts.
Step 6: Commit
Read
in full. Commit per that skill (diff-only message).
Done when: Changes are committed, or there is nothing to commit.
Step 7: Push and reply
Unless
, reply to
every triaged item:
- Draft per verdict shape in .
- Apply the unslop process in
~/.agents/skills/unslop/SKILL.md
- Post using reply commands in . For verdicts, push
before replying; reference the commit SHA. Never post platitudes
("acknowledged", "will fix", "good point", "hope this helps").
- When author is , use dismissal patterns in
.
Done when: Push succeeded (or
); every item has a posted reply
(or
); every reply is concise, humane, and unslopped.
Step 8: Report
Table:
. Include PR URL and commit SHA if any.
Done when: What was fixed, rejected, or discussed is visible at a glance.
Does not handle CI, merge conflicts, or stack restacking (
); never invoke
.