validate-gates

Select and execute validation gates based on changed files.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/brunolimaff-jpg/NOVO-APP --skill validate-gates-brunolimaff-jpg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-gates
Source: https://github.com/brunolimaff-jpg/NOVO-APP/tree/main/.claude/skills/validate-gates
Command: npx skills add https://github.com/brunolimaff-jpg/NOVO-APP --skill validate-gates-brunolimaff-jpg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted cycles and broken releases by ensuring the correct validation checks run before committing or opening a PR.

Core Features & Use Cases

  • Change-aware gate selection: Chooses the appropriate gate(s) based on which files or folders were modified (e.g., prompts, chat UI, TypeScript files, services/tests).
  • Deterministic validation flow: Runs gates in a consistent order (typecheck → tests → contracts → E2E when applicable) and reports pass/fail results per gate.
  • PR and release readiness: Provides clear readiness guidance for commits, PRs, and production/release scenarios, including CI and release-specific validation.

Quick Start

Ask the AI to validate the current changes by running the correct gates for the modified files.

Frequently Asked Questions about validate-gates

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

FAQPage Schema
How do I run the right validation gates based on changed files before a commit?

Validation gates are selected and executed automatically based on which files were modified in the current context, ensuring the correct checks run before committing or opening a pull request.

How does change-aware validation gate selection work for TypeScript and prompt files?

Change-aware validation identifies modified folders or files, such as TypeScript code or prompts, then routes those changes to the appropriate validation gates like typecheck, tests, contracts, or E2E.

What is the correct execution order for pre-PR validation gates like typecheck and E2E?

Validation gates execute in a deterministic order: typecheck runs first, followed by tests, contracts, and E2E when applicable, providing per-gate pass or fail reporting with correction suggestions.

Can I use automated validation gates for release preparation workflows?

Yes, validation gates apply to pre-commit, pre-PR, and release preparation workflows, providing clear readiness guidance for commits, pull requests, and production release scenarios.

How do I get failure listings and correction suggestions when a typecheck or E2E gate fails?

When a validation gate fails, the system reports a failure status per gate and provides specific failure listings along with actionable correction suggestions to fix the issue.