in-the-loop-labs/user-critic
plugin/skills/user-critic/SKILL.md
Fetch human review comments from pair-review and make code changes to address them. Use when the user says "address review feedback", "fix review comments", "address comments", or wants to iterate on code based on feedback left by a human reviewer in pair-review.
$ install --global
skillsauthnpx skillsauth add in-the-loop-labs/pair-review user-criticInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 7:06 AM13.0s1 file scanned
SKILL.md
- name:
- user-critic
- description:
- >
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
repoandprNumberparams. - If no PR exists, use local mode with
path(absolute cwd) andheadSha(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)
Related Skills
in-the-loop-labs/review-requests
development
VerifiedTrustedCommunity
Open outstanding GitHub review requests in pair-review for AI-powered code review. Finds open PRs where my review is pending from the past week and starts pair-review analysis for each. Use when the user says "review requests", "review my PRs", "check review requests", "open review requests", "pair-review my requests", or wants to batch-review their outstanding GitHub review requests.
28SKILL.mdUpdated Apr 20, 2026
in-the-loop-labs/pr
tools
VerifiedTrustedCommunity
Open the GitHub pull request for the current branch in the pair-review web UI. This only opens the browser — it does not run AI analysis or generate suggestions. Once open, the user can browse the diff, leave comments, and trigger analysis from the web UI themselves. Use when the user says "review this PR", "review pull request", "open PR review", or wants to open a pair-review session for the current branch's pull request. If the user wants automated AI analysis of the PR rather than just opening the browser, use the `code-critic:analyze` skill (standalone, requires code-critic plugin) or `pair-review:analyze` skill (requires MCP server) instead. Note that the user can also trigger AI analysis from within the pair-review web UI after opening it.
28SKILL.mdUpdated Apr 20, 2026
in-the-loop-labs/local
tools
VerifiedTrustedCommunity
Open local uncommitted changes for review in the pair-review web UI. This only opens the browser — it does not run AI analysis or generate suggestions. Once open, the user can browse the diff, leave comments, and trigger analysis from the web UI themselves. Use when the user says "review my local changes", "review local", "open local review", or wants to open a pair-review session for uncommitted work in the current directory. If the user wants automated AI analysis of their local changes rather than just opening the browser, use the `code-critic:analyze` skill (standalone, requires code-critic plugin) or `pair-review:analyze` skill (requires MCP server) instead. Note that the user can also trigger AI analysis from within the pair-review web UI after opening it.
28SKILL.mdUpdated Apr 20, 2026
in-the-loop-labs/analyze
tools
VerifiedTrustedCommunity
Perform AI-powered code review analysis using pair-review's server-side analysis engine via MCP. Requires the pair-review MCP server to be connected. For standalone analysis without MCP, use the `code-critic:analyze` skill instead. Starts analysis via the pair-review MCP start_analysis tool, polls for completion, then fetches and presents the curated suggestions. Results are also visible in the pair-review web UI alongside the diff. Use when the user says "analyze in the app", "analyze in the UI", "run server analysis", "analyze with pair-review", or wants analysis results integrated into the pair-review web UI. If the user says something ambiguous like "analyze my changes" or "run analysis" without specifying a method, and both the `code-critic:analyze` and `pair-review:analyze` skills are available, ask whether they want: (1) agent-based analysis (`code-critic:analyze` — results returned directly in the conversation, no server required), or (2) in-app analysis (`pair-review:analyze` — results appear in the pair-review web UI, requires MCP connection). If only one analysis skill is available, use it directly without asking.
28SKILL.mdUpdated Apr 20, 2026