github-pr-comments

A workflow for addressing inline review comments on a GitHub pull request, a proposed code change submitted for review. It gathers each comment with nearby code, tracks the work, applies fixes, and runs verification.

In plain words
What is it for?
It is for fetching pull-request comments, creating a task for each one, applying suggested or inferred changes, and checking the result with the project's Rust commands.
Why use it?
It reduces the chance of missing feedback or changing code without understanding the reviewed section.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/tailcallhq/forgecode/github-pr-comments
Any agent
npx skills add tailcallhq/forgecode --skill github-pr-comments
Clone the repo
git clone --depth 1 https://github.com/tailcallhq/forgecode

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 358 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00058 $0.00358
Opus 5 $0.00029 $0.00179
Sonnet 5 $0.00012 $0.00072
Haiku 4.5 $0.00006 $0.00036

Measured 2d ago against content hash 65f51a4f947a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/pr-comments.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.forge/skills/github-pr-comments/SKILL.md · 57 lines

What it actually says

Resolve Code Review Comments

1. Fetch all comments

Run the bundled script to get every inline comment with its diff hunk:

bash .forge/skills/resolve-code/scripts/pr-comments.sh [PR_NUMBER]

Omit PR_NUMBER to use the current branch's PR.

Each block in the output contains:

  • File : — file path and line number
  • -- code context -- — the diff hunk showing surrounding lines
  • -- comment -- — the reviewer's message

2. Create a todo item per comment

Add one todo for each comment before touching any code. This ensures nothing is missed even when comments span many files.

3. Apply each comment

Work through todos one at a time. There are two comment types:

Suggestion block

Body starts with ```suggestion. Apply the suggested text verbatim as a replacement for the highlighted lines in the diff hunk.

Free-form feedback

Read the comment in the context of the diff hunk, infer the required change, and implement it. When the intent is ambiguous, make the change that best matches the project's conventions and state the assumption clearly.

4. Verify

After all comments are addressed, run:

cargo check && cargo nextest run

Fix any errors before marking the task complete.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 57 lines · 58 tokens per session scan A 65f51a4f947a

Subscribe to this mod's changes

github-pr-comments is a skill published in the GitHub repository tailcallhq/forgecode (7,599 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 358 once invoked, about $0.0003 per session on Opus 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.