testing-quality-gates

Validates code changes through minimum quality gates covering tests, build, lint, and regression.

5|15|Updated Jul 8, 2026

Search Tags:#testing #tdd #bug fix #quality gates #regression #code verification #build validation

Ready to run

npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill testing-quality-gates-clfigueiredo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-quality-gates
Source: https://github.com/clfigueiredo/hermes-infra-skills/tree/main/.hermes/skills/curso-hermes/testing-quality-gates
Command: npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill testing-quality-gates-clfigueiredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unverified code from being delivered by enforcing a minimum set of quality gates after any feature implementation or bug fix, replacing vague claims like "it should work" with real execution evidence. ## Core Features & Use Cases - Minimum Quality Gates: Defines six gates—reproduction, testing, build, lint/typecheck, manual flow, and regression—applied according to the risk of each change. - Change-Type Matrix: Maps change types (UI component, API, database, security, refactor) to the minimum validation required for each. - Structured Validation Report: Produces a final report listing executed commands with results and explicitly declaring what was not validated and why. - Use Case: After fixing a login bug, a student first reproduces the error, writes a test that fails before and passes after the fix, runs the build, and reports the actual command outputs as evidence. ## Quick Start Ask the agent to apply the testing quality gates to validate the bug fix you just implemented and produce the final validation report.

Frequently Asked Questions about testing-quality-gates

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

FAQPage Schema

How do I validate that a bug fix actually works?▼

First reproduce the bug to prove the error exists, then write a test that fails before and passes after the fix. Run the build and lint, confirm the old case does not regress, and report the actual command outputs as evidence.

What tests should I run after changing code?▼

The minimum gate depends on the change type: UI components need visual or manual testing with a clean console, APIs need success, error, and auth tests, database changes need migration and rollback tests, and refactors need the existing suite passing green.

When is E2E testing required versus unit tests?▼

The gate level follows the risk of the change. Unit or integration tests cover most logic changes, while E2E or manual browser flows apply when the change affects user-facing UI behavior or critical end-to-end paths.

Can I skip validation if the change is small?▼

No. The skill prohibits claiming something works without execution evidence and forbids inventing test output. Even small changes require at minimum a build check and an honest report of what was not validated and why.

What should a final validation report include?▼

It lists each executed command with its result, each manual flow tested with its outcome, and a section declaring what was not validated with the real reason. Unrelated build errors must be flagged rather than silently ignored.