What problem does it solve? Teams often apply a fixed, generic test checklist to every change, wasting CI resources on irrelevant checks while missing real verification gaps. This Skill compiles a quality gate tailored to the project's actual stack, framework guidance, and change risk, then keeps it versioned as repository configuration. ## Core Features & Use Cases - Stack-aware quality profile compilation: Detects languages, frameworks, runtimes, and architecture boundaries, then consults current official documentation to define a canonical quality profile stored in the repository (e.g., quality/profile.yaml). - Risk-based verification taxonomy: Maps change types (pure logic, DB migration, UI flow, release) to required test levels such as unit, smoke, integration, contract, and E2E instead of demanding everything every time. - CI resource efficiency: Aligns local and CI gates, prevents duplicate push/pull_request triggers, gates expensive platform matrices, sets concurrency cancellation and timeouts, and treats GitHub Actions usage as a measurable quality invariant. - Use Case: After upgrading a framework or adding a new platform target, run this Skill to recompile the quality profile, repair test infrastructure, and update GitHub Actions workflows so required checks match the new stack. ## Quick Start Use the quality-gate skill to analyze this repository's stack and design a canonical quality profile with fast, integration, and release validation entry points.
