// **Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command.
| name | verify |
| description | **Mandatory** before any commit or push. Run Definition-of-Done checks from change scope and report exact pass/fail per command. |
| argument-hint | auto, minimal, code, proof, proto, full |
Every change must be verified before declaring completion, including documentation-only changes.
If $ARGUMENTS is provided (auto, minimal, code, proof, proto, full),
use it as a hint to prioritize relevant scopes.
If $ARGUMENTS is absent or ambiguous, use automatic scope detection.
Before selecting test commands, run the blast-radius detector script:
cargo make blast-radius
The script returns JSON with these fields:
changed_filesaffected_cratesrisk_flagsdocs_onlyrecommended_scopesrecommended_commandsUse this output as the source of truth for scope selection and command execution order.
If the script is unavailable or fails, use this fallback procedure:
main if available.proto/crates/pessimistic-proof*crates/<crate-name>/docs/, README.md, markdown/adoc/rst/txt prose)affected_crates.
Use docs/knowledge-base/src/architecture.md as the ownership map.risk_flags:
docs_only:
true only when all changed files are documentation/prose and
no runtime code/config/proto files changedfalse otherwiserecommended_scopes:
minimal alwayscode when runtime behavior may changeproof when proof crates changedproto when protobuf schema changedrecommended_commands as exact commands in execution order.If $ARGUMENTS explicitly requests additional scopes,
append the missing scope commands.
minimal always remains required.
If blast-radius reports docs_only: true:
Always run recommended_commands from blast-radius.
Ensure this command is included:
mdbook build docs/knowledge-base/
Skip runtime-heavy scopes (code, proof, proto)
unless the user explicitly requested them via $ARGUMENTS.
Run all matching scopes (scopes are cumulative).
minimal always runs.
Additional scopes come from blast-radius output,
optionally constrained by $ARGUMENTS.
When available,
run recommended_commands directly in the provided order.
cargo check --workspace --tests --all-features
cargo check only type-checks; it does not execute tests.
Never treat a passing cargo check as proof that changes work.
When any scope below matches the changed files, it must also run.
cargo make ci-all
cargo nextest run --workspace
cargo make ci-all runs: format check, clippy, typos,
and clippy on the PP program.
Test selection rules for cargo nextest run (fallback only,
when blast-radius did not provide recommended_commands):
If blast-radius reports broad impact (core types/storage/rpc/proto boundaries or many crates), run:
cargo nextest run --workspace
Otherwise run package-targeted nextest for affected crates first.
If package-targeted tests fail in a way that suggests transitive impact,
escalate to cargo nextest run --workspace.
crates/pessimistic-proof*)cargo make pp-check-vkey-change
If the vkey changed, ask the user for explicit confirmation before running:
cargo make pp-accept-vkey-change
proto/)cargo make generate-proto
Then verify no uncommitted diffs in generated code.
Always report:
Create a git commit following project conventions.
Create a pull request following project conventions.
Review the current conversation and propose structured improvements to skills, documentation, and agent rules.
Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.
Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.
Architecture and agent rules for kurtosis-cdk E2E tests. Load when working on or debugging E2E tests, CI failures in the e2e job, or any task involving bridge testing or kurtosis.