Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
A skill your agent uses when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback
Install Fixing PR Comments
$ npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ReviewStage/stage-cli fixing-pr-comments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fixing-pr-comments .claude/skills/fixing-pr-comments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fixing-pr-comments" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-comments into .claude/skills/fixing-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-pr-comments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-commentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ReviewStage/stage-cli fixing-pr-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fixing-pr-comments .agents/skills/fixing-pr-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fixing-pr-comments" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-comments into .agents/skills/fixing-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-pr-comments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ReviewStage/stage-cli fixing-pr-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fixing-pr-comments .cursor/skills/fixing-pr-comments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fixing-pr-comments" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-comments into .cursor/skills/fixing-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-pr-comments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ReviewStage/stage-cli.git --path .agents/skills/fixing-pr-comments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ReviewStage/stage-cli fixing-pr-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fixing-pr-comments .gemini/skills/fixing-pr-comments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fixing-pr-comments" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-comments into .gemini/skills/fixing-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-pr-comments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ReviewStage/stage-cli fixing-pr-commentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fixing-pr-comments .github/skills/fixing-pr-comments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fixing-pr-comments" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-comments into .github/skills/fixing-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-pr-comments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ReviewStage/stage-cli fixing-pr-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fixing-pr-comments .opencode/skills/fixing-pr-comments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fixing-pr-comments" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/fixing-pr-comments into .opencode/skills/fixing-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-pr-comments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fixing-pr-comments- GitHub stars
- 274
- Token cost
- ~953 tokens
- SKILL.md length
- 295 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback
- Works in 6 steps: Implement the change → Apply forward — find the same pattern… → Quality gate — evaluate the fix against… → …
- A pull request has unresolved review comments that need to be addressed
- SKILL.md covers Workflow, Detect & Fetch, Triage and Fix Loop, plus 2 more sections
- Calls gh and git
What it does
Fixing PR Comments is an agent skill from ReviewStage/stage-cli. Use when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: A viewer for reviewing local code changes in small individual chapters. Works with any AI agent. The licence is MIT.
When your agent uses it
- A pull request has unresolved review comments that need to be addressed
- Asked to fix PR feedback
Example prompts
- “/fixing-pr-comments”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Implement the change
- Apply forward — find the same pattern elsewhere in the codebase and fix those too
- Quality gate — evaluate the fix against every principle in the Implementation Quality section of AGENTS.md. If any principle is violated…
- Verify it compiles/passes
- Commit (one per fix)
- Reply + resolve
What it can do on your machine
Read from SKILL.md and the folder at commit 59b977b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fixing PR Comments loads about 953 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 295 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ReviewStage/stage-cli at commit 59b977b, republished under its MIT licence (© ReviewStage). 295 words, ~953 tokens.
Download SKILL.mdSave it as
.claude/skills/fixing-pr-comments/SKILL.md (or your agent's skills folder).- name
- fixing-pr-comments
- description
- Use when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback
- metadata.internal
- true
Fixing PR Comments
Fetch all unresolved PR threads, triage, fix blockers, resolve the rest.
Workflow
1. DETECT → PR number/repo from current branch
2. FETCH → Unresolved review threads (GraphQL)
3. TRIAGE → Classify each: FIX / RESOLVE / CLARIFY
4. PRESENT → Show triage table, proceed immediately
5. FIX → Implement → verify → commit → reply → resolve (one commit per fix)
6. PUSH → Push all commits
7. RESPOND → Reply to RESOLVE (+ resolve) and CLARIFY threadsDetect & Fetch
gh pr view --json number,url
# GraphQL required — REST lacks isResolved
# Use --input - to avoid gh's -f flag mangling ! in non-null type annotations
gh api graphql --input - <<'GRAPHQL'
{
"query": "query($owner:String!,$repo:String!,$pr:Int!){repository(owner:$owner,name:$repo){pullRequest(number:$pr){reviewThreads(first:100){nodes{id isResolved path line comments(first:10){nodes{id databaseId body author{login}}}}}}}}",
"variables": {"owner": "OWNER", "repo": "REPO", "pr": NUM}
}
GRAPHQLFilter to isResolved: false only.
Triage
Default to RESOLVE. Only FIX what genuinely blocks merge. Resolve everything else with reasoning. Don't gold-plate — ship it.
| Category | Criteria | Action |
|---|---|---|
| FIX | Bugs, security issues, correctness problems — blocks merge | Implement + commit + resolve |
| RESOLVE | Nits, style, "consider X", minor suggestions, pedantic bot feedback, already addressed | Reply with reasoning + resolve |
| CLARIFY | Ambiguous, needs context | Ask in thread, leave open |
Quality flag during triage: If a comment requests something that violates a principle in the Implementation Quality section of AGENTS.md, categorize it as RESOLVE and cite the specific principle it conflicts with.
Present triage table, then proceed immediately:
| # | File:Line | Summary | Category | Reasoning |Fix Loop
For each FIX:
- Implement the change
- Apply forward — find the same pattern elsewhere in the codebase and fix those too
- Quality gate — evaluate the fix against every principle in the Implementation Quality section of AGENTS.md. If any principle is violated, revise before committing.
- Verify it compiles/passes
- Commit (one per fix)
- Reply + resolve:
# Reply (REST — uses databaseId)
gh api repos/{owner}/{repo}/pulls/{pr}/comments/{comment_id}/replies \
-f body="Fixed in <commit_sha>."
# Resolve (GraphQL — REST can't)
gh api graphql --input - <<'GRAPHQL'
{"query": "mutation($id:ID!){resolveReviewThread(input:{threadId:$id}){thread{isResolved}}}","variables": {"id": "THREAD_NODE_ID"}}
GRAPHQLThen git push.
Respond to Remaining
- RESOLVE: Reply with reasoning, then resolve.
- CLARIFY: Ask question, leave open.
Common Mistakes
| Mistake | Fix |
|---|---|
| Fixing before triaging | Triage everything first |
| Fixing nits | RESOLVE with reasoning |
| Accepting quality-violating feedback | RESOLVE comments that conflict with Implementation Quality principles in AGENTS.md |
| Introducing quality violations in fixes | Run quality gate before committing |
| Performative replies ("Great catch!") | State what changed or why not |
| One big commit | One commit per fix |
| Skipping verification | Verify before committing |
| Implementing unclear feedback | CLARIFY, ask first |
| Using REST for resolve | GraphQL required |
| Mixing up ID types | databaseId for REST, id (node ID) for GraphQL |
| RESOLVE without explanation | Always explain |
| Fixing only the flagged line | Search for same pattern, fix all |
© ReviewStage, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/fixing-pr-comments of ReviewStage/stage-cli.
Open the folder on GitHubat commit 59b977b
Compare with similar skills
Fixing PR Comments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fixing PR Comments this skillReviewStage/stage-cli | 274 | — | ~953 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from ReviewStage/stage-cli
All 10 skills in this repoFixing CI
ReviewStage/stage-cli
A skill your agent uses when CI is failing on a branch and you need to diagnose failures from GitHub, fix them locally with iterative verification, and re-push clean commits.
Iterate PR
ReviewStage/stage-cli
A skill your agent uses when a PR is open and the user wants to autonomously monitor and fix PR review comments, CI failures, and rebase conflicts on a recurring loop, or when asked to…
Linear Issue
ReviewStage/stage-cli
A skill your agent uses when creating a Linear issue from the current coding context, or when the user invokes /linear-issue.
Quality Review
ReviewStage/stage-cli
A skill your agent uses when reviewing code changes against AGENTS.md implementation quality standards, or when asked to do an implementation quality review
Rebase Origin Main
ReviewStage/stage-cli
A skill your agent uses when rebasing the current branch onto origin/main, including resolving merge conflicts along the way
Trade Off
ReviewStage/stage-cli
Use at any stage — planning, before implementing, or reviewing code that's already written — to surface high-level trade-offs that could significantly simplify the work.
Related
Categories
Questions about Fixing PR Comments
What does Fixing PR Comments do?
A skill your agent uses when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback. Fixing PR Comments is an agent skill from ReviewStage/stage-cli.
When should I use Fixing PR Comments?
Fixing PR Comments fits situations like: A pull request has unresolved review comments that need to be addressed; asked to fix PR feedback.
How do I install Fixing PR Comments in Claude Code?
Run `npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a claude-code`. Or copy the skill folder (.agents/skills/fixing-pr-comments in ReviewStage/stage-cli) into .claude/skills/fixing-pr-comments in your project. Claude Code loads it when a task matches its description.
How do I install Fixing PR Comments in Codex?
Run `npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a codex`. Or copy the skill folder (.agents/skills/fixing-pr-comments in ReviewStage/stage-cli) into .agents/skills/fixing-pr-comments in your project. Codex loads it when a task matches its description.
Can I use Fixing PR Comments in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ReviewStage/stage-cli --skill fixing-pr-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fixing-pr-comments, .gemini/skills/fixing-pr-comments, .github/skills/fixing-pr-comments and .opencode/skills/fixing-pr-comments in your project.
What does Fixing PR Comments need to run?
Going by SKILL.md and its folder, Fixing PR Comments needs the command-line tools its instructions call (gh and git).
Does Fixing PR Comments access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Fixing PR Comments safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fixing PR Comments use?
Fixing PR Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fixing PR Comments use?
About 953 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fixing PR Comments?
Skills that share tags, products or a category with Fixing PR Comments: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fixing PR Comments?
ReviewStage (a GitHub organization) maintains it in ReviewStage/stage-cli, which has 274 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 7, 2026.
Source: ReviewStage/stage-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.