Purpose
Use this skill as the last step before submitting a change.
It combines two things:
- •verification (build/format/static-analysis/tests)
- •a structured review against this repo’s standards
When to use
Invoke this skill before every submission. It is mandatory.
How to use
- •
Open
references/quality-gate.mdand run the checklist. - •
Run the canonical commands for build / format / static analysis / tests.
- •If a command cannot be run, explain why and provide a reproducible procedure.
- •
Review the diff with the checklists:
- •Readability (naming, comments, control flow, tests)
- •Modularity / coupling / boundaries (worst-level rating)
- •Boundary error handling (translation, no swallowed failures)
- •Observability (logs/metrics/traces for runtime behavior changes)
- •Documentation (requirements / acceptance criteria / verification method)
- •
If you changed C++:
- •
.hpp: verify Doxygen completeness for all declarations (including private). - •
.cpp: verify intent-first comments and a magic-value audit.
- •
- •
Fix findings and repeat until 0 findings remain.
Output expectation
- •Output “0 findings” only when checks and checklist are fully satisfied.
- •Otherwise, list each finding with: location, why it matters, and the concrete fix applied (or the reason it remains).