How do I install the Resolve Review skill?

Run npx skillmds@latest add rockclaver/resolve-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Resolve Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Resolve Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Resolve Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Resolve Review?

rockclaver (@rockclaver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Resolve Review by rockclaver — Agent Skill

Name: Resolve Review
Author: rockclaver

Resolve Review

Fetch GitHub PR review comments, address each in code, resolve the threads, and update the PR. Use when user types /resolve-review, says "address review comments", "fix PR feedback", "resolve review issues", or "respond to code review".

rockclaver 8d26dbe 2 files · 4.5 KB Updated Sep 17, 2026

File contents

resolve-review

PR review comments → fixes → quality gates → resolved threads → updated PR. /resolve-review [N].

1. Identify the PR

gh pr view --json number,title,url,headRefName                        # current branch
gh pr view <number> --json number,title,url,headRefName,baseRefName    # specific PR
gh repo view --json nameWithOwner --jq '.nameWithOwner'                # for below

2. Fetch review comments

gh api repos/{owner}/{repo}/pulls/<number>/comments \
  --jq '[.[] | {id, path, line, body, resolved: false, author: .user.login}]'   # inline
gh pr view <number> --json reviews \
  --jq '.reviews[] | select(.state == "CHANGES_REQUESTED") | {author: .author.login, body: .body}'
gh api repos/{owner}/{repo}/issues/<number>/comments \
  --jq '[.[] | {id, body, author: .user.login}]'   # general

Group by file/theme; list before touching code. Skip unclear ones.

3. Implement & commit — scope each change to its comment, read the file first

git commit -m "fix: <short description> (review comment #<comment-id>)"

4. Quality gates & rebase

npx tsc --noEmit && npm run lint && npm test
git fetch origin && git merge-base --is-ancestor origin/<base-branch> HEAD || git rebase origin/<base-branch>

Never push if a gate fails or conflicts remain.

5. Push & resolve threads

git push origin HEAD
gh api repos/{owner}/{repo}/pulls/<number>/comments/<comment-id>/replies \
  -X POST -f body="Addressed in <commit-sha> — <one-line explanation>"
gh api repos/{owner}/{repo}/pulls/<number>/reviews \
  -X POST -f body="All CHANGES_REQUESTED items addressed." -f event="COMMENT"

6. Update the PR description

CURRENT_BODY=$(gh pr view <number> --json body --jq '.body')
gh pr edit <number> --body "$(cat <<'EOF'
${CURRENT_BODY}

---
## Review response

| # | Comment | Resolution |
|---|---------|------------|
| 1 | @author: "..." | Fixed in <sha> |
EOF
)"

Edge cases: No open PR → ask for a number. Already resolved → skip. Design change → flag. Draft PR → push, tell user to un-draft. Resolve only fixed threads. See REFERENCE.md for language-specific quality gate commands and gh API pagination.

---name: resolve-reviewdescription: Fetch GitHub PR review comments, address each in code, resolve the threads, and update the PR. Use when user types /resolve-review, says "address review comments", "fix PR feedback", "resolve review issues", or "respond to code review".---# resolve-reviewPR review comments → fixes → quality gates → resolved threads → updated PR. `/resolve-review [N]`.### 1. Identify the PR```bashgh pr view --json number,title,url,headRefName # current branchgh pr view <number> --json number,title,url,headRefName,baseRefName # specific PRgh repo view --json nameWithOwner --jq '.nameWithOwner' # for below```### 2. Fetch review comments```bashgh api repos/{owner}/{repo}/pulls/<number>/comments \ --jq '[.[] | {id, path, line, body, resolved: false, author: .user.login}]' # inlinegh pr view <number> --json reviews \ --jq '.reviews[] | select(.state == "CHANGES_REQUESTED") | {author: .author.login, body: .body}'gh api repos/{owner}/{repo}/issues/<number>/comments \ --jq '[.[] | {id, body, author: .user.login}]' # general```Group by file/theme; list before touching code. Skip unclear ones.### 3. Implement & commit — scope each change to its comment, read the file first```bashgit commit -m "fix: <short description> (review comment #<comment-id>)"```### 4. Quality gates & rebase```bashnpx tsc --noEmit && npm run lint && npm testgit fetch origin && git merge-base --is-ancestor origin/<base-branch> HEAD || git rebase origin/<base-branch>```**Never push if a gate fails or conflicts remain.**### 5. Push & resolve threads```bashgit push origin HEADgh api repos/{owner}/{repo}/pulls/<number>/comments/<comment-id>/replies \ -X POST -f body="Addressed in <commit-sha> — <one-line explanation>"gh api repos/{owner}/{repo}/pulls/<number>/reviews \ -X POST -f body="All CHANGES_REQUESTED items addressed." -f event="COMMENT"```### 6. Update the PR description```bashCURRENT_BODY=$(gh pr view <number> --json body --jq '.body')gh pr edit <number> --body "$(cat <<'EOF'${CURRENT_BODY}---## Review response| # | Comment | Resolution ||---|---------|------------|| 1 | @author: "..." | Fixed in <sha> |EOF)"```**Edge cases:** No open PR → ask for a number. Already resolved → skip. Design change → flag. Draft PR → push, tell user to un-draft. Resolve only fixed threads.See [REFERENCE.md](REFERENCE.md) for language-specific quality gate commands and gh API pagination.

Frequently asked questions