Certify
Full verification loop — tests, types, lint, build, and a Playwright browser check for UI projects; collects evidence before any success claim. Use to verify a change is actually green.From its SKILL.md
npx -y skills add Alexander-Tyagunov/magician --skill certifyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.3 KB, as published. Nobody here has run it
/certify — Verification Loop
Run the full verification suite and collect evidence of passing state.
This is tool evidence, not self-review. Every check below is a command whose exit code and output are the proof; nothing here asks the model to re-read its own work and reassure itself. Keep it that way — current models already self-correct, so layering "double-check", "re-verify", or a dedicated verify-my-own-output subagent on top of these commands burns tokens without changing the result. The gate is the clean pass, and it does not move. See lore/model-behavior.md.
Autonomy — approve the plan, then run
Once /certify is invoked and the stack is detected, the required checks run as one autonomous pass: Tests → Type Check → Lint → Build → the UI browser check are the run, not per-step decisions — the check commands, dev server, Monitor tail, read-only git, and kg queries never pause for permission (optionally echo the detected check list once before running). Re-gate only when a failing check needs a real side effect: a Write/Edit fix (or any outward action) — that returns to the owner. Doctrine: lore/autonomy.md.
Required Checks (all must pass)
Run these in order. Stop and fix before continuing if any fail. This is a loop, not a checklist: if a check fails, fix it and re-run from the top — /certify only completes when a single clean pass runs end-to-end with no fixes in between.
1. Tests
Run the test command for the detected stack:
- JavaScript/TypeScript:
npm test - Python:
pytest - Go:
go test ./... - Rust:
cargo test - Java:
mvn testorgradle test
Required: all tests pass, no skipped tests without documented reason.
2. Type Check
- TypeScript:
npx tsc --noEmit - Python:
mypy .(if configured) - Go:
go vet ./... - Rust:
cargo check
Required: zero type errors.
3. Lint
- JavaScript/TypeScript:
npm run lint - Python:
ruff check . - Go:
golangci-lint run - Rust:
cargo clippy
Required: zero lint errors (warnings acceptable if pre-existing). Also hold the code to the project's documented conventions (lore/code-standards.md) — a style rule the reviewer or a code-review.md would flag (e.g. async/await vs .then, import order) is a fail even when the linter is silent about it.
4. Build
Verify the build succeeds (if applicable).
5. Evidence Collection
After all checks pass, write a brief evidence summary:
✅ Tests: N passing, 0 failing
✅ Types: clean
✅ Lint: clean
✅ Build: success
For UI Projects
If the project has a UI:
- Start the dev server (e.g.
npm run dev,yarn dev) in the background - Auto-open the browser to the local URL:
# detect and open URL=$(grep -E '"dev"' package.json | grep -oE 'localhost:[0-9]+' | head -1 || echo "localhost:3000") open "http://$URL" 2>/dev/null || xdg-open "http://$URL" 2>/dev/null || true - Manually verify (or use Playwright if available):
- Golden path works end-to-end
- Edge cases handled gracefully
- No console errors
- If a
/transmuteparity contract exists (.workspace/shared/research/<feature>-parity.md), the behavioral golden fixtures pass (behavioral parity — the G1 gateway), not just the generic golden path
Use the Monitor tool to tail the dev-server output and browser console in the background so a runtime error surfaces as an event mid-check instead of being missed on a one-shot glance.
Completion Signal
Before emitting this signal, apply the verification gate (lore/verification.md): no "passing / clean / done" claim without the actual command output read this run — a remembered result or "should pass" doesn't count. /certify is the runnable suite; that discipline is the reason it exists. The evidence summary must reflect output you read from this pass, not extrapolation.
"Certify complete. Evidence: [summary]. Ready for /scrutinize (code review) or /seal (ship)."