requesting-code-review

Dispatches a code reviewer subagent to evaluate git diffs against requirements before merging.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill requesting-code-review-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill requesting-code-review-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code defects and requirement deviations often go unnoticed until they compound across tasks or reach production. This Skill structures the process of requesting an independent code review so issues are caught early, before merging to main or moving to the next development task. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose reviewer subagent with a precisely crafted prompt template, keeping the reviewer's context separate from your working session. - Structured Feedback Format: Returns findings categorized as Critical, Important, and Minor issues with file:line references, plus strengths, recommendations, and a merge readiness verdict. - Git Range Targeting: Reviews a specific commit range using BASE_SHA and HEAD_SHA so feedback is scoped to exactly what changed. - Use Case: After completing a feature task in subagent-driven development, capture the base and head commit SHAs, dispatch the reviewer with the plan requirements, fix Critical and Important issues, then proceed to the next task with confidence. ## Quick Start Ask the assistant to request a code review of the changes between the previous commit and HEAD using the code-reviewer template 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?▼

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template filled with a description, the requirements, and both SHAs. The reviewer returns categorized issues and a merge readiness verdict.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also useful when stuck, before refactoring as a baseline check, or after fixing a complex bug.

What does the code reviewer subagent check?▼

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness. It verifies the implementation matches requirements, tests cover real behavior, and flags security or backward compatibility concerns with file:line references.

Can the code reviewer modify my working tree?▼

No. The review is strictly read-only on the current checkout. The reviewer uses git show, git diff, and git log to inspect history, and must use a separate temporary worktree if it needs another revision checked out.

What should I do if I disagree with the review feedback?▼

Push back with technical reasoning and show code or tests that prove the implementation works. Fix Critical issues immediately and Important issues before proceeding, but valid disagreement with evidence is explicitly supported.