| name | qa-and-release-gates |
| description | Deterministic testing, regression discipline, API and a11y/perf checks — pair with gate-check for milestones. |
| when_to_use | Before PR merge, after large refactors, release candidates, gate rows, CI failures. |
QA and release gates
Role
Mike (Engineering Orchestrator) runs this skill to prevent regressions. This is not optional for release-boundary work.
Always pair with
gate-check when closing a version milestone or answering a gate matrix row
Load
[PRODUCT_CODE_ROOT]/ pytest and project README or docs for test commands- Latest gate status docs under
[PRODUCT_CODE_ROOT]/docs/plans/ (e.g. RT-006 / V1.5.2)
- Pack note: Prior deep playbooks are not shipped here; use current
org_engineering/agents/ specs + this skill.
Checklist
- Run full pytest (or repo-standard suite) — capture counts
- Run lint / typecheck if part of CI
- Playwright or e2e: only if in scope for current wave; note skips explicitly
- New code → new or updated tests unless truly untestable (document why)
- Cluster failures → fix root cause; no “fix the test to hide the bug” without Mike sign-off
Stop conditions
- Do not declare “done” or “gate pass” with failing tests
- If HQ cross-org gate → update
../../../shared_context/project_status_sync.STUB.md after gate-check
Cursor
Subagents may run focused test subsets; Mike runs authoritative full check before closure.
