no-mistakes

Validates committed code changes through an automated review, test, lint, push, PR, and CI pipeline.

Updated Oct 16, 2025
One-click install
npx skills add https://github.com/hugotown/dotfiles --skill no-mistakes-hugotown
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-mistakes
Source: https://github.com/hugotown/dotfiles/tree/main/agents/skills/no-mistakes
Command: npx skills add https://github.com/hugotown/dotfiles --skill no-mistakes-hugotown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code changes without a consistent validation gate leads to broken tests, lint failures, and unreviewed mistakes reaching pull requests and CI. This Skill drives the no-mistakes local gate so every committed change passes automated review, tests, lint, documentation, push, PR creation, and CI checks before it reaches the configured push target. ## Core Features & Use Cases - Gated validation pipeline: Runs intent, rebase, review, test, document, lint, push, PR, and CI steps through the no-mistakes axi command family, blocking at decision gates until findings are approved, fixed, or skipped. - Two invocation modes: Validate-only mode checks already-committed changes, while task-first mode completes a requested task on a feature branch and then validates it with the user's original intent. - Structured findings workflow: Review findings are classified as auto-fix, no-op, or ask-user, with escalation rules so product-behavior decisions go back to the user. - Use Case: After committing a new feature on a branch, run the gate to have the pipeline review the diff, execute tests and lint, push the branch, open a PR, and monitor CI until checks pass. ## Quick Start Ask the assistant to run /no-mistakes to validate the committed changes on your current feature branch through the full review, test, lint, and CI pipeline.

Frequently Asked Questions about no-mistakes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate code changes before pushing and opening a PR?▼

Commit your work on a feature branch, then run no-mistakes axi run with an --intent describing the goal. The pipeline executes review, test, lint, push, PR, and CI steps, pausing at gates for your decisions until it returns a final outcome.

How do I run the no-mistakes pipeline on my current branch?▼

Ensure the repository is initialized with no-mistakes init and your changes are committed on a non-default branch. Then start a run with no-mistakes axi run --intent "your goal" and respond to each gate with no-mistakes axi respond.

What are the prerequisites for running the no-mistakes gate?▼

The work must be committed on a feature branch, the repository must be initialized with no-mistakes init, and the daemon needs a runnable configured pipeline agent. The no-mistakes doctor command reports configuration problems.

What should I do when a gate returns ask-user findings?▼

Ask-user findings challenge deliberate user intent or product behavior, so relay them verbatim to the user and ask how to proceed. Translate their decision into respond --action fix, approve, or skip rather than deciding yourself.

Why does no-mistakes return checks-passed before the PR is merged?▼

The CI step keeps monitoring the PR in the background after checks go green, so the run returns checks-passed without blocking on the human merge. Ask the user to review and merge the PR using the link in the output.

Can I fix pipeline findings by editing code myself during a run?▼

No. While a run is active the pipeline owns both findings and fixes, so respond with --action fix to have it apply corrections and re-review. Aborting or rerunning mid-run to fix things yourself discards in-flight work.