review

Review completed implementations for correctness and residue before archival.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill review-masta-g3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/masta-g3/rules/tree/main/skills/review
Command: npx skills add https://github.com/masta-g3/rules --skill review-masta-g3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review finished work before archival and commit.

Core Features & Use Cases

  • Identify changed files and assess impact to ensure changes are focused.
  • Enforce quality gates: correctness, minimal surface area, and absence of unnecessary changes or debug statements.
  • Guardrails for residue: flag debug prints, TODOs, and scope drift; for non-trivial changes, invoke the code-critic reviewer subagent.

Quick Start

Review the latest changes and prepare a clean, verifiable handoff before the commit.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code changes before a commit?

To review code changes before a commit, you can analyze completed implementations to ensure correctness. This process guides you through diffs, flags potential issues, and checks adherence to coding standards before archiving.

What is the best way to check for debug residue in a diff?

Checking for debug residue in a diff involves scanning changed files to flag leftover debug prints, TODOs, and scope drift. This ensures a minimal surface area and removes unnecessary changes before the final commit.

Can I review multi-file codebase changes at once?

Yes, you can review multi-file codebase changes at once. The review process applies to both single-file and multi-file changes, identifying all modified files and assessing their impact to keep changes focused.

How does code review handle non-trivial changes?

Code review handles non-trivial changes by invoking a code-critic reviewer subagent. This provides a deeper analysis of complex modifications to enforce quality gates like correctness and minimal surface area.

Why should I verify code quality before archiving?

You should verify code quality before archiving to ensure correctness and prevent scope drift. Verifying work before archival enforces quality gates, removes unnecessary changes, and prepares a clean, verifiable handoff.