maestro:review

Review code changes against specifications, plans, and security guidelines.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill maestro-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro:review
Source: https://github.com/ReinaMacCredy/Maestro-CLI/tree/main/.codex/skills/maestro%3Areview
Command: npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill maestro-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing code changes against project specifications, ensuring quality, security, and adherence to requirements before merging.

Core Features & Use Cases

  • Automated Checks: Runs linters, type checkers, and tests to catch mechanical issues.
  • Dimension-Based Review: Assesses code against intent, quality, security, and product guidelines.
  • Use Case: After a developer implements a new feature, this Skill can be invoked to perform a thorough code review, identifying potential bugs, security vulnerabilities, and deviations from the original plan.

Quick Start

Review the code changes for the current feature branch.

Frequently Asked Questions about maestro:review

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

FAQPage Schema
How do I automate code review against project specifications before merging?

Automated code review checks code changes against project specifications to ensure quality, security, and adherence to plans. It runs linters, type checkers, and tests to catch mechanical issues before merging.

What does dimension-based code review assess?

Dimension-based code review assesses code changes against intent, quality, security, and product guidelines. This approach evaluates multiple dimensions to identify potential bugs, security vulnerabilities, and deviations from the original plan.

How do I check code quality and security vulnerabilities after implementing a feature?

To check code quality and security after feature implementation, invoke a code review process that runs automated checks and manual review dimensions. It identifies potential bugs, security vulnerabilities, and deviations from the original plan.

Can I run automated linters and type checkers in CI/CD for quality assurance?

Yes, automated checks run linters, type checkers, and tests to catch mechanical issues during quality assurance in CI/CD. This ensures implementation correctness and code quality before code changes are merged.

What is the best way to verify test coverage and spec adherence for a feature branch?

The best way to verify test coverage and spec adherence is performing a comprehensive code review against specifications and plans. It validates implementation correctness, code quality, and security vulnerabilities for the feature branch.