confirm
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Pre-computed context
Working tree status: !git status --porcelain 2>/dev/null || echo ""
Changed files (vs HEAD): !git diff --name-only HEAD 2>/dev/null || echo ""
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Recent commits: !git log --oneline -5 2>/dev/null || echo "no commits"
Purpose
/verification:confirm answers "did we build the right thing, and does it work?" — it proves a change achieved its intended outcome. It is an orchestrator, not a reimplementation of the mechanical pass.
Two stages, in order:
| Stage | Question | Mechanism |
|---|---|---|
| 1. Mechanical prerequisite | "does it build, pass tests, satisfy linters?" | delegate /toolchain:check + /toolchain:lint cross-cutting + architecture-test gate. STOP the flow if it fails — can't verify broken code |
| 2. Outcome verification (the core) | "does the change match the plan/intent and function correctly?" | intent match + evidence + (runtime) /testing:run-e2e / live-app observe |
The mechanical pass is a gate, not the point. /toolchain:check owns build+test+lint; /toolchain:lint owns cross-cutting checks. This skill composes them, then does the verification they cannot: did the change accomplish its goal.