github-pr-comments
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.
- License 许可
- Apache-2.0
- 所属仓库
- wasd243/NeoForge
- 最近更新
- 2026-09-24
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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.
02 资源文件 1
- 脚本scripts/pr-comments.sh3.5 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
github-pr-description
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.
execute-plan
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.
create-skill
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.
test-skill
A test skill with resources
minimal-skill
A minimal skill with no resources
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").