address-pr

Fetch GitHub PR review comments, implement the fixes, push, and route the next workflow step.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill address-pr-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: address-pr
Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/address-pr
Command: npx skills add https://github.com/bravros/bravros --skill address-pr-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a pull request review lands, developers must manually read every finding, decide what to fix, commit, push, watch CI, and figure out what happens next. This Skill automates that entire round: it reads the latest review, applies the fixes, ships them, and routes the workflow forward. ## Core Features & Use Cases - Dual-source review fetching: Pulls the latest GitHub bot review via bravros pr-review --latest and merges it with local .planning/pr-reviews/ files, deduplicating findings by file and line. - Classify-then-fix workflow: Checks every finding against the current HEAD before editing, skips already-satisfied items, and applies fixes in priority order (blockers, code issues, style, suggestions). - Push, verify, and stamp: Ships fixes with a conventional commit message, watches CI checks without piping the gate, and writes a commit-sha-keyed review stamp. - Automatic routing: Hands off to the finish, re-review, or merge-decision step based on the severity of what changed. - Use Case: A reviewer leaves three blockers and two nits on your PR. Invoke this Skill and it fetches the review, fixes all five findings, pushes, waits for green CI, stamps the approval, and triggers a re-review — all in one round. ## Quick Start Ask the agent to address the review feedback on the current pull request, optionally passing a PR number or extra instructions like skipping a specific nit.

Frequently Asked Questions about address-pr

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

FAQPage Schema
How do I automatically fix PR review comments with an AI agent?▼

Invoke the address-pr skill with a PR number or on the current branch. It fetches the latest GitHub bot review and local review files, classifies each finding against HEAD, applies fixes in priority order, pushes, and watches CI.

How does the skill decide which review findings to fix?▼

Every finding is checked against the current tree first; already-satisfied items are skipped. Remaining findings are applied in priority order: blockers, code issues, style, then suggestions, touching only files named in the review.

Can I pass instructions instead of a PR number to address-pr?▼

Yes. A numeric argument is treated as the PR number; non-numeric arguments are interpreted as instructions for the round, such as skipping a specific nit or also fixing another issue.

What happens after the fixes are pushed?▼

The skill watches CI with gh pr checks, writes a commit-sha-keyed review stamp via bravros pr-review --write-stamp, then routes: finish if nothing changed, re-review if logic or security files changed, or a merge question for cosmetic-only fixes.

Why does the skill avoid piping gh pr checks output?▼

Piping the watch command through tail returns the pipe's exit status instead of the checks' status, so a failing build would read as success. Output is redirected to a file and the exit code is captured separately.

What are the limitations of automated PR review rounds?▼

After three review rounds on the same PR, the skill recommends a fresh-context deep local review instead of a fourth loop, since repeated new findings on the same diff indicate context drift rather than progress.