Skill

ai-critic

Fetches AI-generated code review suggestions from pair-review, triages validity, applies fixes to actionable ones, and reports summary. Use to address AI feedback after pair-review analysis.

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 AI-generated suggestions from pair-review and make code changes to address the valid ones.

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

AI Critic

Fetch AI-generated suggestions from pair-review and make code changes to address the valid ones.

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 AI suggestions

Call mcp__pair-review__get_ai_suggestions with the review context params. This returns suggestions from the latest analysis run by default.

If the user wants suggestions from a specific analysis run, call mcp__pair-review__get_ai_analysis_runs first to list available runs, then pass the appropriate runId to get_ai_suggestions.

Only active and adopted suggestions are included (dismissed ones are excluded).

If no suggestions are returned, tell the user there are no AI suggestions to address.

Triage and address suggestions

AI suggestions are not human-curated — apply judgment. For each suggestion:

Read the file at the referenced path and lines.
Evaluate the suggestion: is it a real issue, a false positive, or a stylistic preference?
If the suggestion is valid and actionable, make the code change.
If the suggestion is a false positive or not worth addressing, skip it and note why.

Use the ai_confidence field as a signal but not a hard threshold — low-confidence suggestions can still be valid.

Report

After processing all suggestions, provide a summary:

How many suggestions were reviewed
Which ones were addressed (and what changed)
Which ones were skipped (and why)