원클릭으로
no-mistakes
Use for no-mistakes validation, safe push, PR/CI gate, or `/no-mistakes` after committed code changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use for no-mistakes validation, safe push, PR/CI gate, or `/no-mistakes` after committed code changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.
Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.
Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.
| name | no-mistakes |
| description | Use for no-mistakes validation, safe push, PR/CI gate, or `/no-mistakes` after committed code changes. |
Use no-mistakes when the user asks to validate, gate, ship, push safely, open
or update a PR through the no-mistakes process, or invokes /no-mistakes.
Read references/axi-workflow.md before starting, resuming, or responding to a
pipeline run.
Read references/pr-evidence.md before finalizing any PR-backed run.
no-mistakes axi first and respect any active run stateaxi run, axi respond, or any push dry-run, the agent must run
"$HOME/.agents/scripts/ensure-worktree-ready.sh" .; do not ask the user to
run it. Stop if hooks cannot be activated.axi run validates it--intent in the user's words, including product decisions that
are not obvious from the diff.axi respond
instead of manually editing while the run is waiting.ask-user findings verbatim unless the user gave clear unattended
consent such as --yes.gh CI failures, inspect logs in parallel where possible,
batch fixes locally, and rerun the fewest checks.checks-passed or passed, report what was validated, what was found,
and every pipeline fix applied.no-mistakes axi
"$HOME/.agents/scripts/ensure-worktree-ready.sh" .
no-mistakes axi run --intent "<user goal and relevant decisions>"
no-mistakes axi respond --action fix --findings <ids>
no-mistakes axi respond --action approve
no-mistakes axi status
no-mistakes axi logs --step <name> --full
node "$HOME/.agents/skills/no-mistakes/scripts/repair-pr-evidence.mjs"
node "$HOME/.agents/skills/no-mistakes/scripts/repair-pr-evidence.mjs" --e2e-video-required --videos "<local or hosted 2x video>"
help lines instead of guessingchecks-passed means checks are green and the PR is ready for human reviewfailed or cancelled means inspect logs, fix, commit, then rerunDirectory not empty is a recovery state; preserve data and follow tool help--yes only with user consent for unattended actionable gates