requesting-code-review

Dispatches code review agents to verify changes against requirements before merging.

1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/HarmAalbers/claude-requirements-framework --skill requesting-code-review-harmaalbers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/HarmAalbers/claude-requirements-framework/tree/main/plugins/requirements-framework/skills/requesting-code-review
Command: npx skills add https://github.com/HarmAalbers/claude-requirements-framework --skill requesting-code-review-harmaalbers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code changes often ship without structured review, letting bugs, architecture issues, and unmet requirements slip into main branches. This Skill enforces early, frequent review by dispatching specialized review agents against a defined git range. ## Core Features & Use Cases - Pre-commit review dispatch: Run the /pre-commit command to launch code-reviewer, silent-failure-hunter, and tool-validator agents with cross-validation. - Manual subagent review: Dispatch a code-reviewer subagent using a template with git SHAs, implementation summary, and plan requirements. - Severity-based triage: Categorize findings as Critical, Important, or Minor and act on them before proceeding. - Use Case: After finishing a feature task in subagent-driven development, request a review of the diff between the base and head commits, fix Critical issues immediately, and only then move to the next task. ## Quick Start Ask the AI to run the /pre-commit command to review your recent changes before merging.

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 in Claude Code?▼

Run the /pre-commit command, which dispatches code-reviewer, silent-failure-hunter, and tool-validator agents with cross-validation. Alternatively, dispatch a code-reviewer subagent manually using the provided template with your git SHAs.

When should I request a code review during development?▼

Review after each task in subagent-driven development, after completing a major feature, and before merging to main. Optional reviews help when stuck, before refactoring, or after fixing a complex bug.

How do I get the git SHAs needed for a manual code review?▼

Run git rev-parse HEAD~1 for the base SHA (or use origin/main) and git rev-parse HEAD for the head SHA. Pass both into the code-reviewer template so the agent can diff the exact commit range.

What should I do with code review feedback by severity?▼

Fix Critical issues immediately, resolve Important issues before proceeding, and note Minor issues for later. If you believe the reviewer is wrong, push back with technical reasoning and code or tests proving the behavior.

Does requesting a code review satisfy workflow requirements automatically?▼

Completing this skill auto-satisfies the pre_commit_review requirement, but that requirement is deprecated since v2.6 and disabled by default. The /pre-commit command remains available for voluntary use.