no-mistakes

Use when changing agent model or effort configuration, per-run Pi profile pins, adapter mappings, or eval candidate profiles.

Use when changing local branch synchronization, custody recovery, post-review head binding, rebasing or rebase.strategy, private-mirror reconciliation, or force-push safety.

Use when changing CI readiness, forge check collection, reruns, CI timeouts, CI step findings and fix rounds, or PR lifecycle monitoring.

Use when changing daemon startup, singleton ownership, shutdown, logging, event subscriptions, lifecycle commands, or the daemon's login-shell environment.

Use when changing documentation ownership, generated agent guidance, review auto-fix guidance, the combined document+lint housekeeping pass, or the agent memory-file prompt rules.

Use when changing local eval capture, gold labels, diversified and tune sets, matching, replay storage, or eval CLI behavior.

Use when changing recursive gate containment, run worktree placement, bare-gate Git calls, GitHub PR targeting, or post-receive hooks.

Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach the configured push target. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.

Use when changing review sessions, finding decisions, the review fix-round carry, review schema retries, agent timeouts, local Test behavior and its live-validation contract, approval overrides and parked gates, or intent conformance.

Use when changing or migrating the shared require-no-mistakes PR-enforcement action, its live PR lookup, or its workflow caller.

Use when changing subprocess execution, cancellation, process-tree cleanup, orphan reaping, or Windows child hardening.

Use when changing PR body rendering, home-path redaction, artifact path publication, pipeline-attestation markers, or pre-push attestation.

Use when changing macOS release signing, release artifact verification, the release workflow, or the self-update channel manifest.

Use when changing fork routing, forge-profile identity, repository URL persistence, credential redaction, the repo-config trust boundary (trusted-default-branch-only fields), gate-agent instruction neutralization, or repository-declared extra gates.

Use when changing test evidence collection, publication, paths, retention, or scratch-directory cleanup.

Use when adding or changing tests, the e2e harness, fake CLIs in pipeline-step tests, test process isolation, or CI test sharding.