Agent skill

Resolve PR Review Comments

Fetches every inline review comment on a GitHub pull request with its code context, applies each requested change one at a time and verifies the build.

Apache-2.0Auto-check passedDevelopment

Install Resolve PR Review Comments

skills CLI

$ npx skills add tailcallhq/forgecode --skill github-pr-comments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode github-pr-comments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/github-pr-comments .claude/skills/github-pr-comments && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "github-pr-comments" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments into .claude/skills/github-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-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

$skill-installer install https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments

Type 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.

skills CLI

$ npx skills add tailcallhq/forgecode --skill github-pr-comments -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode github-pr-comments --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.forge/skills/github-pr-comments .agents/skills/github-pr-comments && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "github-pr-comments" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments into .agents/skills/github-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-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.

skills CLI

$ npx skills add tailcallhq/forgecode --skill github-pr-comments -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode github-pr-comments --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.forge/skills/github-pr-comments .cursor/skills/github-pr-comments && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "github-pr-comments" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments into .cursor/skills/github-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-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

$ gemini skills install https://github.com/tailcallhq/forgecode.git --path .forge/skills/github-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.

skills CLI

$ npx skills add tailcallhq/forgecode --skill github-pr-comments -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode github-pr-comments --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.forge/skills/github-pr-comments .gemini/skills/github-pr-comments && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "github-pr-comments" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments into .gemini/skills/github-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-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.

GitHub CLI

$ gh skill install tailcallhq/forgecode github-pr-comments

Installs 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).

skills CLI

$ npx skills add tailcallhq/forgecode --skill github-pr-comments -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .github/skills && cp -r skills-src/.forge/skills/github-pr-comments .github/skills/github-pr-comments && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "github-pr-comments" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments into .github/skills/github-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-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.

skills CLI

$ npx skills add tailcallhq/forgecode --skill github-pr-comments -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tailcallhq/forgecode github-pr-comments --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.forge/skills/github-pr-comments .opencode/skills/github-pr-comments && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "github-pr-comments" agent skill from https://github.com/tailcallhq/forgecode/tree/main/.forge/skills/github-pr-comments into .opencode/skills/github-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-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: github-pr-comments
GitHub stars: 7.6k
Token cost: ~396 tokens
SKILL.md length: 173 words
Files: 2 (incl. scripts)
Skills in repo: 14
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Fetches every inline review comment on a GitHub pull request with its code context, applies each requested change one at a time and verifies the build.

Works in 4 steps: Fetch all comments → Create a todo item per comment → Apply each comment → …
Working through reviewer feedback on an open pull request
SKILL.md covers 1. Fetch all comments, 2. Create a todo item per…, 3. Apply each comment and 4. Verify
Runs Shell scripts from its folder; calls cargo and bash

What it does

A bundled script, scripts/pr-comments.sh, prints every inline comment with the file and line, the diff hunk around it and the reviewer's message. It uses the current branch's pull request unless you give a PR number. Before touching any code, the agent adds one todo item per comment, so none are missed when comments are spread over many files, and then works through them one by one.

A comment that starts with a suggestion block is applied verbatim over the highlighted lines. Free-form feedback is read in the context of its diff hunk and implemented, following project conventions and stating the assumption when the intent is unclear. When all comments are addressed, the agent runs cargo check and cargo nextest run and fixes any errors before calling the work complete.

When your agent uses it

Working through reviewer feedback on an open pull request
Applying a batch of suggestion blocks without copying them by hand
Making sure no inline review comment is overlooked

Example prompts

“Resolve the review comments on the open PR for this branch.”
“Address the PR feedback on my current branch and run the checks afterward.”
“Work through the inline review comments one by one and list the assumptions you made.”

Requirements

Bash, to run the comment-fetching script
Rust with cargo and cargo-nextest for the final check

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Fetch all comments
Create a todo item per comment
Apply each comment
Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 92a5699. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- cargo
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Resolve PR Review Comments loads about 396 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 173 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~74
When it runs · the whole SKILL.md, loaded when a task matches: ~396

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); the scripts in this folder are not scanned.

SKILL.md

The full file from tailcallhq/forgecode at commit 92a5699, republished under its Apache-2.0 licence (© tailcallhq). 173 words, ~396 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr-comments/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: github-pr-comments
description: Resolve inline code review comments on a GitHub PR. Use when asked to "resolve review comments", "address PR feedback", "fix PR comments", or "work through review comments". Fetches every inline comment with its surrounding code context, then applies each change systematically.

Resolve Code Review Comments

1. Fetch all comments

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

bash

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:

bash

cargo check && cargo nextest run

Fix any errors before marking the task complete.

Files

SKILL.md and 1 other file (scripts) in .forge/skills/github-pr-comments of tailcallhq/forgecode.

SKILL.md
scripts/pr-comments.sh

Open the folder on GitHubat commit 92a5699

Compare with similar skills

Resolve PR Review 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.

Resolve PR Review Comments compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Resolve PR Review Comments this skilltailcallhq/forgecode	7.6k	—	~396	Automated safety check: Pass	Apache-2.0	today
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
GitHub Review Iterationprisma/orm	48k	—	~2.2k	Automated safety check: Pass	Apache-2.0	today
PR Finalize Reviewmicrosoft/garnet	12k	—	~3.1k	Automated safety check: Pass	MIT	today
PR Review State Fetchprisma/orm	48k	—	~767	Automated safety check: Pass	Apache-2.0	today
Fastlane Pull Request Reviewfastlane/fastlane	42k	—	~550	Automated safety check: Pass	MIT	today

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.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
GitHub Review Iteration
prisma/orm
Official
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
48k GitHub stars~2.2k tokensUpdated today
DevelopmentAuto-check passed
PR Finalize Review
microsoft/garnet
Official
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
12k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
PR Review State Fetch
prisma/orm
Official
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
48k GitHub stars~767 tokensUpdated today
DevelopmentAuto-check passed
Fastlane Pull Request Review
fastlane/fastlane
Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.
42k GitHub stars~550 tokensUpdated today
DevelopmentAuto-check passed
Pull Request Reviewer for daisyUI
saadeghi/daisyui
Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report.
43k GitHub stars~766 tokensUpdated 7 days ago
DevelopmentAuto-check passed

More from tailcallhq/forgecode

All 14 skills in this repo

Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
7.6k GitHub starsUsed in 1 repo~4.5k tokens
Auto-check passed
Forge CLI Debug Workflow
tailcallhq/forgecode
Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.
7.6k GitHub starsUsed in 1 repo~1.6k tokens
Auto-check passed
FIXME Resolver
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
7.6k GitHub stars~1.1k tokensUpdated today
Auto-check passed
Reasoning Serialization Tests
tailcallhq/forgecode
Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.
7.6k GitHub stars~1k tokensUpdated today
Auto-check passed
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
7.6k GitHub starsUsed in 1 repo~1.1k tokens
Auto-check passed
Release Notes Writer
tailcallhq/forgecode
Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.
7.6k GitHub stars~1.4k tokensUpdated today
Auto-check passed

Works with

GitHub

Questions about Resolve PR Review Comments

What does Resolve PR Review Comments do?

Fetches every inline review comment on a GitHub pull request with its code context, applies each requested change one at a time and verifies the build. sh, prints every inline comment with the file and line, the diff hunk around it and the reviewer's message. It uses the current branch's pull request unless you give a PR number.

When should I use Resolve PR Review Comments?

Resolve PR Review Comments fits situations like: working through reviewer feedback on an open pull request; applying a batch of suggestion blocks without copying them by hand; making sure no inline review comment is overlooked.

How do I install Resolve PR Review Comments in Claude Code?

Run `npx skills add tailcallhq/forgecode --skill github-pr-comments -a claude-code`. Or copy the skill folder (.forge/skills/github-pr-comments in tailcallhq/forgecode) into .claude/skills/github-pr-comments in your project. Claude Code loads it when a task matches its description.

How do I install Resolve PR Review Comments in Codex?

Run `npx skills add tailcallhq/forgecode --skill github-pr-comments -a codex`. Or copy the skill folder (.forge/skills/github-pr-comments in tailcallhq/forgecode) into .agents/skills/github-pr-comments in your project. Codex loads it when a task matches its description.

Can I use Resolve PR Review 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 tailcallhq/forgecode --skill github-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/github-pr-comments, .gemini/skills/github-pr-comments, .github/skills/github-pr-comments and .opencode/skills/github-pr-comments in your project.

What does Resolve PR Review Comments need to run?

Going by SKILL.md and its folder, Resolve PR Review Comments needs a shell for the scripts in its folder and the command-line tools its instructions call (cargo and bash). Our summary lists: Bash, to run the comment-fetching script; Rust with cargo and cargo-nextest for the final check.

Does Resolve PR Review Comments access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Resolve PR Review 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Resolve PR Review Comments use?

Resolve PR Review Comments is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Resolve PR Review Comments use?

About 396 tokens (SKILL.md is roughly 1.6k 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 Resolve PR Review Comments?

Skills that share tags, products or a category with Resolve PR Review Comments: PR Babysitter (openinterpreter/openinterpreter, 69k stars), GitHub Review Iteration (prisma/orm, 48k stars), PR Finalize Review (microsoft/garnet, 12k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Resolve PR Review Comments?

tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,642 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: tailcallhq/forgecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Resolve PR Review Comments

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Resolve Code Review Comments

1. Fetch all comments

2. Create a todo item per comment

3. Apply each comment

Suggestion block

Free-form feedback

4. Verify

Files

Compare with similar skills

Similar skills

More from tailcallhq/forgecode

Related

Questions about Resolve PR Review Comments