review

Orchestrate two-stage code review for spec compliance and quality.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/mikemyl/verified-development --skill review-mikemyl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mikemyl/verified-development/tree/main/skills/review
Command: npx skills add https://github.com/mikemyl/verified-development --skill review-mikemyl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by ensuring spec compliance and conducting targeted quality reviews, reducing errors and improving code quality.

Core Features & Use Cases

  • Spec Compliance: Ensures that code meets the specified requirements before proceeding to quality review.
  • Quality Review: Runs targeted quality agents based on the changes made to the code.
  • Use Case: Use this Skill to review a feature's code, ensuring it complies with the spec and passes quality checks before merging.

Quick Start

Run the 'review' skill to start the two-stage review process for the current feature.

Frequently Asked Questions about review

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

FAQPage Schema
What is a two-stage code review process for spec compliance?

A two-stage code review process first validates code against specification requirements, then executes targeted quality checks. This approach ensures the software development meets functional requirements before running quality agents to review the actual code changes.

How do I automate code review for spec compliance and quality assurance?

You can automate code review by running a skill that orchestrates quality agents to check codebase changes. It first verifies spec compliance, then performs a targeted quality review to ensure the code meets all requirements before merging.

Does the code review process require access to the codebase?

Yes, spec compliance and quality review require direct access to the codebase. The review agents must be able to execute within the development environment to analyze the actual code changes and validate them against specifications.

What is the best way to ensure code meets specifications before merging?

The best way to ensure code meets specifications is using a structured review process that checks spec compliance first. After verifying the feature against the spec, targeted quality agents run additional checks to validate overall code quality before merge.

Can I run quality agents on specific code changes instead of the whole codebase?

Yes, the quality review stage runs targeted quality agents based specifically on the changes made to the code. This ensures the quality assurance process focuses only on the modified areas rather than scanning the entire codebase.

When should I use automated quality agents instead of manual code review?

Use automated quality agents when you need consistent spec compliance and targeted quality checks for feature development. It reduces human error and streamlines the software development process by validating code changes before merging.