pr-polish

Alternate /pr-review and /pr-address until pull request checks pass.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ghpworkuse-web/train --skill pr-polish-ghpworkuse-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-polish
Source: https://github.com/ghpworkuse-web/train/tree/main/AutoGPT/.claude/skills/pr-polish
Command: npx skills add https://github.com/ghpworkuse-web/train --skill pr-polish-ghpworkuse-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple PR reviews and addressing feedback across rounds to reach a merge-ready state without lingering issues.

Core Features & Use Cases

  • Alternates /pr-review and /pr-address until all findings are resolved, ensuring no new inline comments or unresolved threads.
  • Polls CI and reviewer activity to confirm stability, with safeguards like a maximum rounds cap and automatic re-checks after each address step.
  • Works with PRs identified by URL or current branch and can be invoked repeatedly until mergeable.

Quick Start

Start by invoking the skill with a PR URL or on the current branch to begin iterative polishing until the PR is merge-ready.

Frequently Asked Questions about pr-polish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request reviews until all feedback is resolved?

Automate iterative pull request polishing by alternating review and address cycles until all GitHub checks pass and the PR reaches a merge-ready state. The process continuously validates state snapshots to ensure no lingering inline comments or unresolved threads remain before completion.

What's the best way to handle multiple rounds of code review on GitHub without missing comments?

Handling multiple code review rounds requires alternating automated review and feedback addressing steps, polling CI status and reviewer activity between each cycle. State validation rechecks GitHub state before completion to safeguard against late bot comments or newly introduced unresolved threads.

Can I use a branch name instead of a URL to start polishing a pull request?

Yes, pull request polishing works with PRs identified by either a direct URL or the current branch name. Invoking the skill on a target branch automatically locates the associated PR and begins the iterative review and address cycles.

Does pr-polish stop automatically if CI checks fail or there are too many review rounds?

Yes, a configurable maximum round limit caps the iterative cycles to prevent infinite loops. The skill polls CI gates and reviewer activity after each address step, stopping automatically if checks remain failing or the maximum round limit is reached.

Why does my automated PR review show unresolved threads after the process completes?

Unresolved threads appearing after completion may result from late bot comments added after the final state validation. The skill rechecks GitHub state before completion to catch these, but newly posted comments occurring after the last snapshot recheck could remain unresolved.