$npx -y skills add stevesolun/ctx --skill no-mistakesValidate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
| 1 | # no-mistakes |
| 2 | |
| 3 | `no-mistakes` is a local git gate. It validates committed branch changes before |
| 4 | they reach upstream and reports decision points in machine-readable TOON. |
| 5 | |
| 6 | ## Preconditions |
| 7 | |
| 8 | - Work is committed. |
| 9 | - Current branch is a feature branch, not the default branch. |
| 10 | - The repository has been initialized with `no-mistakes init`. |
| 11 | - The intent is explicit: what the user wanted to accomplish, not only a diff |
| 12 | summary. |
| 13 | |
| 14 | ## Run |
| 15 | |
| 16 | ```sh |
| 17 | no-mistakes axi run --intent "<what the user set out to accomplish>" |
| 18 | ``` |
| 19 | |
| 20 | Use the user's exact objective as the intent, enriched with material decisions |
| 21 | and constraints learned during the work. |
| 22 | |
| 23 | ## Decision Loop |
| 24 | |
| 25 | If output contains a `gate:` object, inspect each finding: |
| 26 | |
| 27 | - `auto-fix`: make the mechanical fix, then respond with `fix`. |
| 28 | - `no-op`: approve or continue when nothing needs changing. |
| 29 | - `ask-user`: stop and relay the finding to the user before responding. |
| 30 | |
| 31 | Useful commands: |
| 32 | |
| 33 | ```sh |
| 34 | no-mistakes axi respond --action approve |
| 35 | no-mistakes axi respond --action fix --findings <id1,id2> --instructions "<guidance>" |
| 36 | no-mistakes axi respond --action skip |
| 37 | no-mistakes axi status |
| 38 | no-mistakes axi logs --step <name> --full |
| 39 | no-mistakes axi abort |
| 40 | ``` |
| 41 | |
| 42 | ## Output Contract |
| 43 | |
| 44 | - `checks-passed`: CI is green and the PR is ready for human review/merge. |
| 45 | - `passed`: the gate completed. |
| 46 | - `failed` or `cancelled`: inspect output and fix the reported issue. |
| 47 | |
| 48 | Do not silently approve `ask-user` findings unless the user explicitly gave |
| 49 | standing consent such as `--yes`. |