// Comprehensive verification system to run before committing, creating PRs, or shipping.
Use Beads (`bd`) as the durable task-management system for work that needs priorities, dependencies, status tracking, and cross-session continuity.
Turn a one-line objective into a step-by-step construction plan where every step has a self-contained context brief. Designed for work that spans multiple sessions or agents.
Treat diagnosis as a first-class phase before fixing a bug, unstable behavior, or weird operational issue.
Use contracts, templates, and durable markdown artifacts consistently when a workflow needs handoffs, plans, context bundles, decisions, or verification evidence.
Use this when designing an internal tool or operational app where the safest path is to prove the workflow and UI before locking in backend structure.
Create a practical understanding of a repository or a large area before detailed work begins.
| name | verification-loop |
| description | Comprehensive verification system to run before committing, creating PRs, or shipping. |
| pack | skills-core |
Comprehensive verification system to run before committing, creating PRs, or shipping.
Run all phases sequentially. If any phase fails, stop and fix before continuing.
# Python
uv run python -m py_compile src/main.py
# TypeScript
npm run build
If build fails, STOP. Fix build errors before any other verification.
# Python
uv run mypy src/
# TypeScript
npx tsc --noEmit
Report all type errors. Fix critical ones before continuing.
# Python
uv run ruff check .
# TypeScript
npm run lint
Auto-fix where safe: ruff check --fix .
# Python
uv run pytest --tb=short
# TypeScript
npm test
Report: total / passed / failed / skipped.
Check for:
sk-, api_key=, passwords in source).env files staged for commitprint(), console.log(), debugger)git diff --stat
git diff --name-only
Review each changed file for:
Capture the result as a verification-report artifact when the task is running
under a recipe-driven workflow:
contracts/verification-report/CONTRACT.mdcontracts/verification-report/TEMPLATE.mdVERIFICATION REPORT
===================
Build: [PASS/FAIL]
Types: [PASS/FAIL] (X errors)
Lint: [PASS/FAIL] (X warnings)
Tests: [PASS/FAIL] (X/Y passed)
Security: [PASS/FAIL] (X issues)
Diff: [X files changed]
Verdict: [READY / NOT READY]
Issues to Fix:
1. ...
2. ...
During long sessions, set mental checkpoints:
Run /verify at each checkpoint. Do not let errors accumulate.
/review (no point reviewing code that does not build)/plan implementation is complete