No Mistakes

Overview

Use no-mistakes as the repo's finished-feature workflow: inspect readiness, verify the local branch, push through the no-mistakes remote when approved, attach to the run, and help the user react to pipeline findings until PR/CI is ready.

Guardrails

• Treat git push no-mistakes, bare no-mistakes -y, and CI auto-fix runs as remote-affecting operations. Ask before running them unless the user explicitly requested a push/PR flow.
• Prefer explicit repo commands in .no-mistakes.yaml over agent auto-detection for repeatable gates.
• Use bundled scripts with a generic Python runner (python3 first, then python) and no external dependencies.
• Run commands from the target Git repo root when initializing, configuring, or checking status.
• Use command -v and no-mistakes doctor for prerequisites. Avoid hard-coded local binary paths in reusable instructions.
• Treat install commands as a fallback only when no-mistakes is missing or broken.

Deterministic Check

Start with the bundled health check when inspecting an existing repo. Resolve scripts/check_no_mistakes.py relative to this skill folder, then run it with whichever Python command exists: