Menu
Deterministic testing, regression discipline, API and a11y/perf checks — pair with gate-check for milestones.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AI feature engineering — llama, embeddings, RAG quality, inference reliability, cost/token discipline.
System architecture, structured code review bar, and technical documentation.
Backend HTTP API, SQLite, Qdrant, integration contracts, schema and migration safety.
Maturity / inspection pass over [ORG_NAME] code sections (BCS). Load your org’s code-sections ledger, run verify ladder, update shared_context summary on main when columns change.
Data pipelines, ingest, remediation, entity quality — PDF/docs through to vector store.
Decision continuity, handoffs, supersession — Engineering Orchestrator (Mike) accountable; pair with session-notes.
| 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. |
Mike (Engineering Orchestrator) runs this skill to prevent regressions. This is not optional for release-boundary work.
gate-check when closing a version milestone or answering a gate matrix row[PRODUCT_CODE_ROOT]/ pytest and project README or docs for test commands[PRODUCT_CODE_ROOT]/docs/plans/ (e.g. RT-006 / V1.5.2)org_engineering/agents/ specs + this skill.../../../shared_context/project_status_sync.STUB.md after gate-checkSubagents may run focused test subsets; Mike runs authoritative full check before closure.