skill-requesting-code-review

Dispatches an independent reviewer subagent to evaluate completed code changes against plans and requirements.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/longdang193/project-OS-starter --skill skill-requesting-code-review-longdang193
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-requesting-code-review
Source: https://github.com/longdang193/project-OS-starter/tree/main/generated_agents/claude/skills/skill-requesting-code-review
Command: npx skills add https://github.com/longdang193/project-OS-starter --skill skill-requesting-code-review-longdang193

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code changes often proceed to merge or handoff without independent verification, letting defects, plan deviations, and architecture problems cascade into later work. This Skill structures the request for an independent code review so issues are caught before integration. ## Core Features & Use Cases - Independent Review Dispatch: Fills a reviewer prompt template with description, requirements, evidence context, approved deviations, and Git base/head SHAs so the reviewer evaluates only the work product. - Severity-Calibrated Feedback: Returns strengths, Critical/Important/Minor issues with file:line references, recommendations, and a PASS/FAIL/BLOCKED verdict. - Optional OCR Advisory Overlay: Supports a preparation JSON file with scope identity verification and protected-path handling for immutable Git ranges. - Use Case: After finishing a feature task, capture the approved base SHA and head SHA, dispatch a reviewer subagent with the filled template, fix Critical and Important findings, then continue to the next task or merge. ## Quick Start Ask the agent to request an independent code review of the completed changes between the approved base commit and HEAD before merging.

Frequently Asked Questions about skill-requesting-code-review

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

FAQPage Schema
How do I request a code review for completed changes?▼

Capture the approved base SHA from the active plan and the head SHA from git rev-parse HEAD, then dispatch an independent reviewer subagent using the code-reviewer.md template filled with description, requirements, evidence, and deviations.

When should code review be requested in a development workflow?▼

Review is mandatory after completing a major feature, before merging to main, and when the active lifecycle requires it. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What does the code reviewer return after reviewing a Git range?▼

The reviewer returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and an assessment with a PASS, FAIL, or BLOCKED verdict plus brief technical reasoning.

Can the reviewer modify the working tree during review?▼

No. The review is strictly read-only on the checkout. The reviewer uses git show, git diff, and git log to inspect history and must use a separate temporary directory if a working copy of another revision is needed.

What are the limitations of the optional OCR preparation overlay?▼

OCR is advisory only and range-only, gated to the v1 schema with OCR_NO_UPDATE=1. It never reconstructs or narrows the Git inventory, protected paths stay metadata-only, and OCR never selects the PASS, FAIL, or BLOCKED verdict.