Risk-proportional verification for Bondery monorepo changes. Maps changed files to npm workspaces and shared-package consumers, runs the fastest relevant lint, type, policy, test, contract, build, and runtime checks, then reviews staged and unstaged diffs without requiring commits. Use after implementing or refactoring, before handoff or a PR, when asked to verify/test/check changes, or when deciding which Bondery quality gates apply.
Risk-proportional verification for Bondery monorepo changes. Maps changed files to npm workspaces and shared-package consumers, runs the fastest relevant lint, type, policy, test, contract, build, and runtime checks, then reviews staged and unstaged diffs without requiring commits. Use after implementing or refactoring, before handoff or a PR, when asked to verify/test/check changes, or when deciding which Bondery quality gates apply.
metadata
{"version":"1.0.0","namespace":"bondery"}
Bondery Verification Loop
When to use
After implementing a feature, bug fix, or refactor
Before handoff, PR, or marking a Plane task done
When the user asks to verify, test, validate, or check work
When unsure which pnpm run gates apply to the current diff
When not to use
Architecture-only planning — write → verify: steps instead (see references/risk-and-reporting.md)
Deep security review — use bondery-security
Legal/subprocessor reconciliation — use bondery-legal
Post-push CI triage — use Cursor babysit skill
Dependency upgrade matrices — use .agents/workflows/chores/UPGRADE-PACKAGES.md
Non-negotiables
Define success criteria first — each item maps to a command or explicit manual check (bondery-core AGENTS.md §4).
Scope to the diff — inspect changed, staged, and untracked files; never assume HEAD~1.
Fast checks first — non-mutating Biome on changed files before full-repo gates.
Risk expands scope — shared packages, auth, migrations, and contracts pull in consumer checks.
Loop until pass — fix failures, re-run the failed gate, repeat.
Report honestly — list skipped checks, blockers, generated drift, and residual risk.
Read-only by default — do not stage, commit, or amend unless the user explicitly asked.
Domain rules stay in owner skills — complete linked checklists; do not duplicate them here.
Workflow
Scope — git status --short, git diff, git diff --cached (or session edits if Git unavailable).
Classify risk — low / standard / high (see references/risk-and-reporting.md).
