Use this page after choosing a path from User Paths. These are
short command sequences for common jobs. They do not add new behavior; they
compose existing tokmd and xtask surfaces.
Run:
tokmd --format md --top 8
tokmd analyze --preset risk --format mdOpen first: terminal output.
This gives a quick repo shape, then a risk-oriented analysis pass. It does not run tests, review a PR, or prove release readiness.
Run:
tokmd cockpit \
--base origin/main \
--head HEAD \
--review-packet-dir .tokmd/review
cargo xtask review-packet-check \
--dir .tokmd/review \
--json target/tokmd/review-packet-check.jsonOpen first:
.tokmd/review/comment.md.tokmd/review/review-map.md.tokmd/review/evidence.jsontarget/tokmd/review-packet-check.json
This gives a packet summary, review work order, evidence state, and packet verifier receipt. It is not a merge verdict.
Run:
cargo xtask affected \
--base origin/main \
--head HEAD \
--json-output target/proof/affected.json
cargo xtask ci-plan \
--base origin/main \
--head HEAD \
--labels-json '[]' \
--json-out target/ci/ci-plan.json \
--route-json-out target/ci/proof-pack-route.json \
--no-budget-annotations
cargo xtask proof \
--profile affected \
--base origin/main \
--head HEAD \
--plan \
--plan-json target/proof/proof-plan.json \
--evidence-json target/proof/proof-evidence.jsonOpen first:
target/proof/affected.jsontarget/ci/proof-pack-route.jsontarget/proof/proof-plan.jsontarget/proof/proof-evidence.json
This tells you which files changed, which proof scopes matched, and which CI risk/proof packs and skipped-by-policy lanes explain route selection before reading which commands are required or advisory. It does not execute the planned proof.
Run when observation artifacts already exist:
cargo xtask proof-observation-status \
--observations-dir target/proof-observations \
--json target/proof-observations/proof-observation-decision.json \
--summary-md target/proof-observations/proof-observation-decision.md
cargo xtask proof-observation-status-check \
--decision target/proof-observations/proof-observation-decision.json \
--json target/proof-observations/proof-observation-decision-check.jsonOpen first:
target/proof-observations/proof-observation-decision.mdtarget/proof-observations/proof-observation-decision.jsontarget/proof-observations/proof-observation-decision-check.json
This summarizes observed proof status and promotion criteria. It does not promote proof, enable Codecov upload, or make advisory proof required.
Run after generating review and proof artifacts:
tokmd handoff \
--preset risk \
--budget 128k \
--strategy spread \
--review-packet-dir .tokmd/review \
--review-packet-check target/tokmd/review-packet-check.json \
--affected target/proof/affected.json \
--proof-plan target/proof/proof-plan.json \
--out-dir .handoffIf the review packet contains .tokmd/review/proof/proof-pack-route.json,
handoff links that packet-local route automatically. Use --proof-route <path>
only when a different route receipt should own the proof-route link.
Open first:
.handoff/work-order.md.handoff/manifest.json.handoff/code.txt.handoff/review-links.json.handoff/proof-links.json
Give the agent work-order.md first. Treat proof routes as selection and
skip-policy receipts, not execution proof. Treat missing, stale, degraded, or
unavailable evidence as work to resolve, not as passing proof.
Run: open the browser runner, load a GitHub repo or local files, and download the browser-safe receipt.
Open first: the browser UI summary, then the downloaded receipt.
Next native command for real PR review:
tokmd cockpit \
--base origin/main \
--head HEAD \
--review-packet-dir .tokmd/reviewBrowser mode is a no-install trial lens. It does not provide native filesystem access, git-history enrichers, cockpit packets, gates, context bundles, handoff bundles, or AST capability claims.
Run:
cargo xtask publish-surface --json --verify-publish
cargo xtask version-consistencyOpen first: publish-surface output or saved JSON, then version-consistency output.
This checks package-surface and version-readiness evidence. It does not publish crates, create tags, create GitHub releases, or approve release mutation.
For release-facing files, pair this with affected proof planning as shown in Release readiness.