completion-verifylisted

# Completion Verify Run the quality gates a task must clear before you tell the user it is done. ## Usage ``` /completion-verify # verify current uncommitted work /completion-verify --staged # verify staged changes only ``` ## Behavior ### Phase 1: Diff scope ```bash git diff --stat git diff --name-only ``` Confirm the changed files match what the task actually required. Flag anything unrelated. ### Phase 2: Build ```bash npm run build 2>&1 | tail -20 || pnpm build 2>&1 | tail -20 ``` Stop and fix before continuing if the build fails. ### Phase 3: Type check ```bash npx --no-install tsc --noEmit 2>&1 | head -30 # or: pyright . 2>&1 | head -30 ``` ### Phase 4: Lint ```bash npm run lint 2>&1 | head -30 # or: ruff check . 2>&1 | head -30 ``` ### Phase 5: Tests ```bash npm test 2>&1 | tail -50 # or: pytest -q 2>&1 | tail -50 ``` Report pass/fail counts. Never disable or skip a failing test to make this pass. ### Phase 6: Quick security check ```bash git diff | grep -E "sk-|api[_-]?key|password\s*=|BEGIN.*PRIVATE KEY" | head -10 ``` ### Phase 7: Verdict ``` COMPLETION CHECK Scope: N files, all within task Build: PASS/FAIL Types: PASS/FAIL (N errors) Lint: PASS/FAIL (N warnings) Tests: PASS/FAIL (X/Y passed) Security: PASS/FAIL (N findings) Verdict: READY / NOT READY ``` Only claim the task is done when every gate that applies to the project passes. ## Examples **Clean finish:** ``` /completion-verify → 3 files changed, bui