/verify
Verify post-build before committing. Matches change type to check list. Writes a marker the pre-commit hook reads. Runs after each task.
/verifyType it bare, or paste it with loose context after — Claude figures out the rest.
Tests run but scope-drift and missed acceptance and ADR violations slip through.
Post-build gate that matches change type to check list. Runs before commit not after.
Takes in
- Change type or scope hint
Returns
- Check results per gate
- Blocking findings
- Ready-to-commit signal
What it does
Post-build verification gate. Run /verify after any task before committing code. I look at the type of change. I run the matching verification. I confirm the production build passes.
When everything clears, I write a marker at state/markers/verify/<branch>.marker. The pre-commit-gate hook reads that marker. Without it, the hook blocks your commit. This is the check between "tests green" and "safe to ship."
Read the full skill
The complete instructions live at .claude/skills/verify/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Also relevant in: Build.
Why this phase: Post-build verification gate — matches change type to appropriate verification.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- luminary
- A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
- hook
- A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
- adopter
- A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
Shipped by @kingofrock · Read the essays
/pattern-review
Review code through the lens of world-class engineering patterns — GoF, Fowler, SOLID, DDD. Flag violations and suggest improvements. Complements /architect-review which is system-level.
/visual-review
Visual UX review — screenshot a rendered page and evaluate against design tokens, usability standard, and Creative Director / Designer luminaries. Requires Playwright MCP.