review

Reviews git diffs against coding standards and originating specs using parallel sub-agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often conflate two separate questions — does the code follow project conventions, and does it implement what was actually requested — causing one axis to mask failures in the other. This Skill separates those concerns into independent parallel reviews of any diff since a fixed point. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (conformance to documented coding standards like CODING_STANDARDS.md or CONTRIBUTING.md) and a Spec review (fidelity to the originating issue, PRD, or spec file) as parallel sub-agents that don't pollute each other's context. - Automatic spec discovery: Locates the originating spec via issue references in commit messages, user-provided paths, or PRD files under docs/, specs/, or .scratch/. - Side-by-side reporting: Aggregates both reports under separate headings without merging or reranking, ending with a per-axis summary. - Use Case: Before merging a feature branch, ask for a review since main to simultaneously verify the diff follows repo conventions and faithfully implements the linked issue. ## Quick Start Ask the assistant to review the changes since main using the review skill, and it will validate the fixed point, find the spec and standards sources, and report both axes side by side.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review all changes since a specific commit or branch?▼

Provide a fixed point such as a commit SHA, branch name, tag, or HEAD~5, and the review uses git diff with three-dot notation against the merge-base. The fixed point is validated with git rev-parse before any review begins, so bad refs fail early.

How do I check if code matches the original issue or PRD?▼

The Spec axis compares the diff against the originating spec, found via issue references in commit messages, a user-provided path, or PRD files under docs/, specs/, or .scratch/. It reports missing requirements, scope creep, and incorrect implementations with quoted spec lines.

What happens if there is no spec for the changes being reviewed?▼

If no spec is found and the user confirms none exists, the Spec sub-agent is skipped and the final report notes that no spec was available. The Standards review still runs normally against documented coding standards.

Why run standards and spec reviews as separate sub-agents?▼

Separating the axes prevents one from masking the other: code can follow every standard but implement the wrong thing, or implement the right thing while breaking conventions. Parallel sub-agents also keep each review's context unpolluted.

What are the limitations of diff-based code review?▼

The review only sees changes in the diff, so pre-existing issues outside the modified hunks are not evaluated. It also depends on the repo containing documented standards and a discoverable spec; without them, one or both axes produce limited findings.