pr-polish
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-reviewer) frequently post late after CI settles; a single green snapshot is not sufficient.
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.
More from significant-gravitas/autogpt
pr-review
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
42vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
29worktree
Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.
20pr-address
Address PR review comments and loop until CI green and all comments resolved. TRIGGER when user asks to address comments, fix PR feedback, respond to reviewers, or babysit/monitor a PR.
20backend-check
Run the full backend formatting, linting, and test suite. Ensures code quality before commits and PRs. TRIGGER when backend Python code has been modified and needs validation.
17pr-test
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.
15