maestro:verification

Name: maestro:verification
Availability: InStock
Author: ReinaMacCredy

Enforce build, test, and lint verification before completion claims.

Updated Mar 13, 2026

Search Tags:#code quality #testing #ci/cd #verification #regression #commit hygiene

Ready to run

npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill maestro-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maestro:verification
Source: https://github.com/ReinaMacCredy/Maestro-CLI/tree/main/.codex/skills/maestro%3Averification
Command: npx skills add https://github.com/ReinaMacCredy/Maestro-CLI --skill maestro-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents dishonest and inefficient claims of work completion by enforcing a rigorous, evidence-based verification process before any code is committed, merged, or reported as done.

Core Features & Use Cases

Mandatory Verification Gates: Ensures all code is built, tested, and linted before claiming completion.
Multi-Scope Verification: Provides distinct verification checklists for tasks, phases, and entire features.
Use Case: Before merging a feature branch, you must run bun run build, bun test, and git diff main...HEAD --stat to confirm no regressions were introduced and all acceptance criteria are met.

Quick Start

Always run the verification commands and examine their output before claiming any work is complete.

Frequently Asked Questions about maestro:verification

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

FAQPage Schema

How do I prevent premature claims of code completion before making a commit?▼

Prevent premature completion claims by mandating an evidence-based verification protocol that requires running build, test, and lint commands before committing. Reviewing their output proves correctness and stability.

What is evidence-based verification in software development?▼

Evidence-based verification is a protocol requiring concrete proof of correctness through executed build, test, and lint outputs. It addresses dishonest work status claims by mandating output review before reporting tasks or features as done.

How do I verify no regressions were introduced before merging a feature branch?▼

Verify regressions before merging by running build, test, and lint commands, then reviewing their output. This protocol ensures all acceptance criteria are met and confirms code stability before claiming completion.

Does this verification protocol support different scopes like tasks, phases, and features?▼

Yes, the verification protocol supports multi-scope checking by providing distinct verification checklists for individual tasks, development phases, and entire features. This ensures comprehensive evidence-based validation across all project levels.

Why should I run lint and test commands before creating a pull request?▼

Run lint and test commands before pull requests to enforce commit hygiene and prevent unsubstantiated claims of work status. Reviewing command output provides concrete proof of correctness and confirms no regressions were introduced.

Can I use this verification process for CI/CD pipeline regression checks?▼

Yes, you can use this verification process for CI/CD regression checks. It mandates running build and test commands while reviewing their output to ensure stability and prevent regressions before claiming any work is complete.