Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
antinomyhq avatar

Github Pr Comments

  • 4 installs
  • 7.5k repo stars
  • Updated August 5, 2026
  • antinomyhq/forge

github-pr-comments is a Claude Code skill that resolves inline code review comments on a GitHub pull request by fetching each comment with its diff context and applying the change.

About

This skill resolves inline code review comments on a GitHub pull request. A developer runs it after a reviewer leaves feedback, and it fetches every inline comment with its surrounding diff hunk, creates a todo per comment, then applies each change. It applies GitHub suggestion blocks verbatim and infers the required change for free-form feedback, then runs cargo check and cargo nextest to verify.

  • Fetches every inline PR comment with its diff hunk via a bundled script
  • Creates one todo per comment so nothing is missed across many files
  • Applies suggestion blocks verbatim and infers changes for free-form feedback, then verifies with cargo check and nextest

Github Pr Comments by the numbers

  • 4 all-time installs (skills.sh)
  • Ranked #901 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

github-pr-comments capabilities & compatibility

Capabilities
code review · pr description
Works with
github
Use cases
code review
From the docs

What github-pr-comments says it does

Resolve inline code review comments on a GitHub PR.
SKILL.md
Add one todo for each comment before touching any code. This ensures nothing is missed even when comments span many files.
SKILL.md
npx skills add https://github.com/antinomyhq/forge --skill github-pr-comments

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4
repo stars7.5k
Last updatedAugust 5, 2026
Repositoryantinomyhq/forge

What it does

Systematically apply reviewer feedback on an open GitHub pull request without missing any inline comment.

Who is it for?

Working through reviewer feedback on an open GitHub PR systematically

When should I use this skill?

Asked to resolve review comments, address PR feedback, or fix PR comments

What you get

Every inline review comment is addressed and the change set is verified to compile and pass tests.

  • Applied code changes addressing each PR comment
  • Verified build via cargo check and cargo nextest run

By the numbers

  • one todo item created per review comment

Files

SKILL.mdMarkdownGitHub ↗

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.

Related skills

FAQ

How does it find the review comments?

It runs a bundled script (pr-comments.sh) that outputs every inline comment with its file path, line number, and diff hunk.

How does it handle GitHub suggestion blocks versus free-form comments?

Suggestion blocks are applied verbatim as a replacement for the highlighted lines; free-form feedback is read in context and implemented.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.