The command
One line. AcePilot reads the codebase, traces the root cause through the call stack, writes the minimal fix, adds a regression test, and commits. Here's what happens behind the scenes:
What AcePilot does
Orient
Reads the file structure and relevant code paths. No guessing — understands the problem first before touching a single line.
Root cause
Traces the bug through the call stack. Checks recent git history for when it broke — symptoms versus causes, always the cause.
Confidence gate
Reversible fix (two-way door) executes immediately. If touching core auth or payment logic, shows a 3-line plan first and waits.
Fix
Writes the minimal change. Follows existing code style, naming conventions, and indentation. No drive-by refactors.
Regression test
Adds a test case that would have caught this bug. Runs it. Green only — never commits a failing test.
Qualify
@reviewer checks the fix matches the original bug spec. DONE or BLOCKED — never silent, never ambiguous.
What you get
- Root cause identified in the commit history, not just the symptom
- Minimal fix — only the lines that need to change
- Regression test that would have caught this earlier
- Specialist security review if auth or tokens were touched
- Git commit: "acepilot: fix [bug description]"
- Qualifier: fix matches original bug spec
Real example
A /acepilot go fix session cookie not persisting session
traced the bug to a missing SameSite=Lax attribute on the
Set-Cookie header — set 3 years ago in a "temporary" fix
that shipped. @security flagged it as P0. Fixed in the same session.
When to use this
- You have a bug report and want it fixed without context-switching
- You want root cause analysis, not just symptom patching
- You need a regression test to prevent recurrence
- You want a security check on any auth or session code touched
Try it yourself
$ cd acepilot && ./acepilot-14.0/install.sh
# In your project directory
$ claude
> /acepilot go fix [your bug description]