Define quality gates and pass criteria
quality-eval-coreskillsetup L2★0
Sheshiyer/skill-clusters ↗What it does
Define quality gates (write/commit/CI/ship) and evidence ladder for all tests
Best for
Meta-framework that unifies how TDD, E2E, benchmark, and audit spokes define what done means and route failures to earliest gate
Inputs
- · test output
- · measurement baseline
Outputs
- · pass@k score
- · evidence classification
Preconditions
Tests deterministic or pass@k methodology applied
Failure modes
- · Single green run claimed as pass
- · Evidence ladder skipped (asserted instead of measured)
- · Same model writes and reviews (blind-spot correlation)
Trust signals
- · Four-gate model (write/commit/CI/ship)
- · Evidence ladder (asserted→ran→tested→measured→reproduced)
- · pass@k discipline for stochastic tasks