no-mistakes
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.
- License 许可
- MIT
- 所属仓库
- stevesolun/ctx
- 最近更新
- 2026-10-15
- Stars
- ★ 592
- Forks
- 69
01 前言 Front Matter
- 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
03 SKILL.md 正文
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
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 withfix.no-op: approve or continue when nothing needs changing.ask-user: stop and relay the finding to the user before responding.
Useful commands:
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.failedorcancelled: inspect output and fix the reported issue.
Do not silently approve ask-user findings unless the user explicitly gave
standing consent such as --yes.
04 同仓库更多 Skills
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing toolboxes with a team.
skill-router
Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.
repo-stats-autoupdate
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
find-skills
Discover installable agent skills from ctx's shipped Skills.sh catalog, the Skills.sh search API, and the npx skills CLI. Use when a user asks whether a skill exists, wants to add/update a skill, or needs a repeatable procedure for finding candidate skills safely.
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
writing-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.