.forge/skills/github-pr-comments/SKILL.md
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.
npx skillsauth add antinomyhq/forgecode github-pr-commentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 messageAdd one todo for each comment before touching any code. This ensures nothing is missed even when comments span many files.
Work through todos one at a time. There are two comment types:
Body starts with ```suggestion. Apply the suggested text verbatim as a
replacement for the highlighted lines in the diff hunk.
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.
After all comments are addressed, run:
cargo check && cargo nextest run
Fix any errors before marking the task complete.
tools
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
development
Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
testing
A test skill with resources