validation

Validate orchestration phase outputs across builds, linting, tests, and manual checks.

453|34|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/josstei/maestro-gemini --skill validation-josstei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/josstei/maestro-gemini/tree/main/skills/validation
Command: npx skills add https://github.com/josstei/maestro-gemini --skill validation-josstei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate orchestration phase outputs and project integrity across builds, linting, tests, and manual verifications to prevent quality regressions.

Core Features & Use Cases

  • Structured, multi-step validation pipeline (build, lint, unit tests, integration tests, manual checks)
  • Post-phase validation and diagnostic reporting to diagnose failures and guide remediation
  • Incremental validation and strictness modes to balance speed and rigor across pipelines
  • Project-type detection and cross-language applicability to enforce consistent quality standards

Quick Start

Run the validation phase after code changes to ensure builds, linting, tests, and manual checks pass.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I automate build, lint, and test validation after code changes?

Automated validation performs end-to-end checks on phase outputs to ensure build correctness and project integrity. It applies a structured pipeline covering builds, linting, unit and integration tests, and manual verifications to prevent quality regressions.

What is a structured validation pipeline for software engineering projects?

A structured validation pipeline is a multi-step process that verifies project integrity through sequential stages. It detects project types and applies cross-language standards to enforce consistent quality across builds, linting, unit tests, integration tests, and manual checks.

Can I use automated validation across different programming languages and project types?

Yes, automated validation supports cross-language applicability through project-type detection. This mechanism identifies the specific project context and enforces consistent quality standards across diverse languages and project types without requiring language-specific configuration.

How do I balance validation speed and rigor in a CI pipeline?

You can balance validation speed and rigor using incremental validation and strictness modes. These configurable options allow the pipeline to selectively run checks, optimizing execution time while maintaining necessary quality enforcement across different pipeline stages.

Why do I need post-phase diagnostic reporting for build and test failures?

Post-phase diagnostic reporting is needed to diagnose failures and guide remediation after validation checks. It provides detailed feedback on build, lint, and test errors, enabling developers to quickly identify root causes and correct quality regressions.