Skip to main content

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.

설치로 이동

소스 정보

저장소
tailcallhq/forgecode
최근 소스 활동
2026년 4월 2일 10:49
감지된 SKILL.md 언어
영어
스타
7,633
포크
1,464

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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.
GitHub에서 보기