requesting-code-review

Review code changes against requirements using a git diff range.

Updated May 5, 2026
One-click install
npx skills add https://github.com/XCmiaow/cc-deploy --skill requesting-code-review-xcmiaow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/XCmiaow/cc-deploy/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/XCmiaow/cc-deploy --skill requesting-code-review-xcmiaow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents defects, quality regressions, and missed requirements by inserting a disciplined review step into the development workflow before changes compound.

Core Features & Use Cases

  • Early, mandatory review cadence: Enforces review after each task in subagent-driven development, after major feature completion, and before merging to main.
  • Requirement-anchored evaluation: Sends the reviewer precisely crafted context tied to the implementation description, plan/requirements, and the git commit range.
  • Actionable feedback loop: Directs you to fix Critical issues immediately, fix Important issues before proceeding, track Minor issues for later, and push back with technical reasoning if feedback is incorrect.
  • Baseline review against a defined diff: Uses BASE_SHA and HEAD_SHA to review only the relevant change window and supports checking code quality, architecture, testing, and production readiness.

Quick Start

Request code review after implementing your latest task by providing the implemented summary, the plan/requirements reference, and the BASE_SHA/HEAD_SHA diff range to the code-reviewer subagent.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate code review for a specific git diff range before merging to main?

Automating code review for a specific git diff range involves providing the implementation summary, requirements, and BASE_SHA/HEAD_SHA commit hashes. This dispatches a reviewer subagent to evaluate the targeted change window for production readiness and code quality before merging to main.

What is the best way to structure a pre-merge code review in a subagent workflow?

The best way to structure a pre-merge code review in a subagent workflow is to enforce a mandatory review cadence after each task. Dispatch the code-reviewer subagent with templated context tied to your requirements and git diff to catch issues early.

How do I manage code review severity levels and remediation decisions?

To manage code review severity levels, fix Critical issues immediately, fix Important issues before proceeding to the next task, and track Minor issues for later resolution. You can also push back on feedback with technical reasoning if the review is incorrect.

Does this code review process work for checking production readiness after a bug fix?

Yes, this code review process works for checking production readiness after complex bug fixes. By anchoring the evaluation to the specific git diff range and requirements, it ensures the bug fix does not introduce quality regressions or miss original specifications.

What inputs do I need to provide for a baseline review against a defined diff?

To perform a baseline review against a defined diff, you need to provide the BASE_SHA and HEAD_SHA inputs, the implemented task summary, and the plan or requirements reference. This scopes the review strictly to the relevant change window.