stage-cli: Skill for Claude Code

.agents/skills/fixing-pr-comments/SKILL.md

fixing-pr-comments is a skill for Claude Code, Codex from ReviewStage/stage-cli. It costs 27 tokens per session (946 once invoked), scanned A, original, MIT.

A workflow for handling unresolved comments on a GitHub pull request, which is a proposed code change waiting for review. It finds each open discussion, sorts it into an action, and handles the result.

In plain words
What is it for?
Use it to find open pull-request discussions, decide which require code changes, verify and commit those changes, reply to reviewers, close resolved discussions, and push the commits.
Why use it?
It prevents review comments from being missed or handled inconsistently. It separates changes that block merging from comments that only need an explanation or a decision.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is ReviewStage/stage-cli's own configuration. It tells Claude Code and Codex how to work on stage-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything stage-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ReviewStage/stage-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ReviewStage/stage-cli/main/.agents/skills/fixing-pr-comments/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ReviewStage/stage-cli

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fixing-pr-comments

README.md
[![agentmods](https://agentmods.dev/badge/skills/reviewstage/stage-cli/fixing-pr-comments/github.svg)](https://agentmods.dev/skills/reviewstage/stage-cli/fixing-pr-comments)
Your own site
<a href="https://agentmods.dev/skills/reviewstage/stage-cli/fixing-pr-comments"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/fixing-pr-comments/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for fixing-pr-comments

Your own site · 80×15
<a href="https://agentmods.dev/skills/reviewstage/stage-cli/fixing-pr-comments"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/fixing-pr-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 946 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00946
Opus 5.5 $0.00011 $0.00378
Sonnet 5.5 $0.00005 $0.00189
Haiku 4.5 $0.00003 $0.00095

Measured 1mo ago against content hash 8425c8638c68, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fixing-pr-comments scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/fixing-pr-comments/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 threads

Detect & 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}
}
GRAPHQL

Filter 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:

  1. Implement the change
  2. Apply forward — find the same pattern elsewhere in the codebase and fix those too
  3. Quality gate — evaluate the fix against every principle in the Implementation Quality section of AGENTS.md. If any principle is violated, revise before committing.
  4. Verify it compiles/passes
  5. Commit (one per fix)
  6. Reply + resolve:

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 103 lines · 27 tokens per session scan A 8425c8638c68

Subscribe to this mod's changes

fixing-pr-comments is a skill published in the GitHub repository ReviewStage/stage-cli (274 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 946 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens