Verifiable Quality Gates

When you write, review, or rely on an automated check — a CI guard, custom lint rule, schema/config validator, or architecture fitness function: make it provably detect what it claims. Every check gets a committed test that FAILS when the check is neutralized (proven mechanically by a mutation gate), fails closed, and proves each invariant at the layer that owns it. Triggers on: adding/changing a CI check or guard, a check that 'passes' but might not be catching anything, a green build you don't fully trust, making quality gates self-proving.

techfleetworks Updated

File contents

techfleetworks/enterprise-software-AI-skills commit 36c49eea33

Frequently asked questions

npx get-skill add techfleetworks/verifiable-quality-gates