Fetch human-curated review comments from pair-review and make code changes to address each one.
Determine review context
Determine whether this is a local review or a PR review:
If the user explicitly says "local", use local mode.
Otherwise, determine the GitHub owner, repo, and PR number for the current branch. If a PR exists, use PR mode with repo and prNumber params.
If no PR exists, use local mode with path (absolute cwd) and headSha (git rev-parse HEAD) params.
Fetch comments
Call mcp__pair-review__get_user_comments with the review context params.
If no comments are returned, tell the user there's nothing to address.
Address each comment
For each comment returned:
Read the file at the referenced path and lines.
Understand what the reviewer is asking for — it may be a bug fix, a refactoring request, a question, or a style change.
Make the code change that addresses the feedback.
If the comment is a question or unclear, explain your interpretation and what you changed.
Report
After addressing all comments, provide a summary:
Which files were changed
What was done for each comment
Any comments that were ambiguous or could not be addressed (explain why)
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: in-the-loop-labs-pair-review-user-critic3description: Address Review Feedback4---56# Address Review Feedback78Fetch human-curated review comments from pair-review and make code changes to address each one.910## Determine review context1112Determine whether this is a local review or a PR review:13141. If the user explicitly says "local", use local mode.152. Otherwise, determine the GitHub owner, repo, and PR number for the current branch. If a PR exists, use PR mode with `repo` and `prNumber` params.163. If no PR exists, use local mode with `path` (absolute cwd) and `headSha` (`git rev-parse HEAD`) params.1718## Fetch comments1920Call `mcp__pair-review__get_user_comments` with the review context params.2122If no comments are returned, tell the user there's nothing to address.2324## Address each comment2526For each comment returned:27281. Read the file at the referenced path and lines.292. Understand what the reviewer is asking for — it may be a bug fix, a refactoring request, a question, or a style change.303. Make the code change that addresses the feedback.314. If the comment is a question or unclear, explain your interpretation and what you changed.3233## Report3435After addressing all comments, provide a summary:36- Which files were changed37- What was done for each comment38- Any comments that were ambiguous or could not be addressed (explain why)3940---41> Converted and distributed by [TomeVault](https://tomevault.io/claim/in-the-loop-labs) — claim your Tome and manage your conversions.42<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/in-the-loop-labs-pair-review-user-critic 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.
Address Review Feedback It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
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.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io