requesting-code-review

Routes code changes to specialized review agents based on change type and context.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill requesting-code-review-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill requesting-code-review-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right depth and type of code review for each change is error-prone: teams either under-review risky diffs (auth, payments, AI-authored code) or over-review trivial ones, and AI-generated code hides defect classes that pass the happy path. This Skill routes every change to the correct review agent(s) so reviews are mandatory, proportionate, and consistent before merge. ## Core Features & Use Cases - Review agent routing: Maps your change to one of 25+ specialized reviewers (pr, spec, tests, security, language, CI, IaC, API contract, E2E, accessibility, and more), with /review all running the four PR-scoped agents in parallel. - AI-authored code posture: Treats every diff as AI-generated by default, checking for hallucinated APIs, hardcoded secrets, missing authorization, and happy-path-only logic, with mandatory security review for auth, payments, PII, and security boundaries. - Dispatch discipline: Enforces file-path-based artifact passing, single fix-agent per findings list, re-review until PASS, and severity-based action (Critical / Important / Minor). - Use Case: After implementing a feature with subagents, run /review pr after each task to catch issues early, then /review all before merge — no merge proceeds with any Critical finding. ## Quick Start Ask the AI to review your current changes by saying "review my PR" and it will route to the appropriate review agents automatically.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a code review before merging a PR?

Run /review all before merge to dispatch the pr-reviewer, spec-impl-reviewer, test-quality-reviewer, and security-reviewer in parallel. The merge is blocked if any agent returns a Critical finding.

Which code review type should I use for my change?

Use /review pr as the minimum for every PR, /review security for auth or data-access changes, /review tests when tests were modified, and /review spec to verify implementation against acceptance criteria. Targeted reviews run via /review <type>.

How should AI-generated code be reviewed differently?

AI-authored diffs require checking for hallucinated APIs, hardcoded secrets, missing authorization, and happy-path-only logic, since AI code reads cleanly while hiding these defect classes. Code touching auth, payments, or PII must always go through security review regardless of size.

What happens when a code reviewer returns findings?

Dispatch one fix agent with the complete findings list, then re-dispatch the same reviewer and repeat until it passes. Critical issues are fixed immediately, Important issues before merge, and Minor issues can be deferred.

When should I not use the full review suite?

The /review all suite is for PR-scoped review; use /review full only for periodic whole-codebase audits after milestones or before releases. Specialized reviewers like ci-reviewer or iac-reviewer run on demand and are excluded from /review all.