stevesolun/ctx / imported-skills/no-mistakes/skills/no-mistakes
no-mistakes
VerifiedValidate 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
name: no-mistakes
description: >
Validate 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.
user-invocable: true
---
# no-mistakes
`no-mistakes` is a local git gate. It validates committed branch changes before
they reach upstream and reports decision points in machine-readable TOON.
## Preconditions
- Work is committed.
- Current branch is a feature branch, not the default branch.
- The repository has been initialized with `no-mistakes init`.
- The intent is explicit: what the user wanted to accomplish, not only a diff
summary.
## Run
```sh
no-mistakes axi run --intent "<what the user set out to accomplish>"
```
Use the user's exact objective as the intent, enriched with material decisions
and constraints learned during the work.
## Decision Loop
If output contains a `gate:` object, inspect each finding:
- `auto-fix`: make the mechanical fix, then respond with `fix`.
- `no-op`: approve or continue when nothing needs changing.
- `ask-user`: stop and relay the finding to the user before responding.
Useful commands:
```sh
no-mistakes axi respond --action approve
no-mistakes axi respond --action fix --findings <id1,id2> --instructions "<guidance>"
no-mistakes axi respond --action skip
no-mistakes axi status
no-mistakes axi logs --step <name> --full
no-mistakes axi abort
```
## Output Contract
- `checks-passed`: CI is green and the PR is ready for human review/merge.
- `passed`: the gate completed.
- `failed` or `cancelled`: inspect output and fix the reported issue.
Do not silently approve `ask-user` findings unless the user explicitly gave
standing consent such as `--yes`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |