
Polish a Pull Request
Alternate review and address passes until a PR is ready to merge.
Install
npx skills add Significant-Gravitas/AutoGPT --skill pr-polish -g -a claude-code -y- Repository
- Significant-Gravitas/AutoGPT188k
- Category
- Git and review
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable, no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.
PR Polish
Goal. Drive a PR to merge-ready by alternating /pr-review and /pr-address until all of the following hold:
- The most recent
/pr-reviewproduces zero new findings (no new inline comments, no new top-level reviews with a non-empty body). - Every inline review thread reachable via GraphQL reports
isResolved: true. - Every non-bot, non-author top-level review has been acknowledged (replied-to) OR resolved via a thread it spawned.
- Every non-bot, non-author issue comment has been acknowledged (replied-to).
- Every CI check is
conclusion: "success"or"skipped"/"neutral", none"failure"or still pending. - Two consecutive post-CI polls (≥60s apart) stay clean, no new threads, no new non-empty reviews, no new issue comments. Bots (coderabbitai, sentry, autogpt-pr-reviewer) frequently post late after CI settles; a single green snapshot is not sufficient.
- No requested-but-unanswered review. If a
/reviewcomment was posted on the PR and the review bot has not replied yet, quiet polls do not count toward condition 6, keep polling until the review lands or the wait budget expires. See Waiting on a requested bot review.
Do not stop at a fixed number of rounds. If round N introduces new comments, round N+1 is required. Cap at _MAX_ROUNDS = 10 as a safety valve, but expect 2, 5 in practice.
TodoWrite
Before starting, write two todos so the user can see the loop progression:
Round {current}: /pr-review + /pr-address on PR #{N}, current iteration.Final polish polling: 2 consecutive clean polls, CI green, 0 unresolved, runs after the last non-empty review round.
Update the current round counter at the start of each iteration; mark completed only when the round's address step finishes (all new threads addressed + resolved).
