requesting-code-review

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

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill requesting-code-review-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill requesting-code-review-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, missing requirements, and architectural issues compound across tasks. This Skill structures the review request so a fresh reviewer subagent evaluates only the work product, not your session history. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer template with what was implemented, the plan, and git SHAs so the reviewer gets precise context. - Severity-Based Feedback Loop: Categorizes findings as Critical, Important, or Minor, with clear rules for which issues block progress. - Workflow Integration: Defines mandatory review points for subagent-driven development, plan execution, and pre-merge checks. - Use Case: After completing a task that adds verification functions, you capture the base and head commit SHAs, dispatch the reviewer subagent with the plan reference, receive categorized feedback, fix the Important issues, and continue to the next task. ## 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 continuing.

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 changes?▼

Capture the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent with what was implemented, the plan reference, and the SHA range. The reviewer returns categorized issues and a merge readiness verdict.

When should code review be requested during development?▼

Review is mandatory after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What context does the code reviewer subagent need?▼

The reviewer needs five placeholders filled: what was implemented, the plan or requirements, the base SHA, the head SHA, and a brief description. It reviews the git diff between the two SHAs, never your session history.

How are code review issues categorized by severity?▼

Issues are split into Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, optimizations). Critical issues must be fixed immediately and Important issues before proceeding.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer if needed.