Skill

user-critic

Fetches human review comments from pair-review for local changes or GitHub PRs and applies code changes to address each one. Useful for iterating on reviewer feedback.

Git

Github

git-workflow

code-quality

Install

npx claudepluginhub in-the-loop-labs/pair-review --plugin pair-review

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Fetch human-curated review comments from pair-review and make code changes to address each one.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

next-compile

1 file

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

vercel-next-js-2

139.2k

Stats

Parent Repo Stars27

Parent Repo Forks6

Last CommitFeb 3, 2026

Actions

View Source View Plugin View on GitHub View README

Address Review Feedback

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)