Fix

Fix repairs a defect: it captures the problem, proves the bug, makes the smallest safe change, verifies it, and closes with evidence.

When to use

• A bug with observable wrong behavior.
• You can describe the expected behavior and the actual behavior.
• The change should stay small and focused, not a redesign.

What it does

• Frame. Pins the problem boundary, scope, constraints, and proof plan.
• Verify (baseline). Runs the regression command before any edit to prove the bug fails, and snapshots the pre-fix git state.
• Analyze. Gathers context, then diagnoses the root cause. The diagnosis stays honest about uncertainty when the bug doesn't cleanly reproduce.
• Act. Applies one focused change.
• Verify. Runs the proof, computes the change-set against the baseline, and reruns the regression command to confirm it now passes.
• Review. Independent audit of the change at medium process and above.
• Close. Emits the result. It can only report fixed when verification passed, the regression was proved and now clears, and the change-set matches the declared files.

low process drops the review pass; medium and high keep it. Fix has no checkpoints. See Power, process, and modes.

Example

/circuit:run fix the off-by-one in pagination

circuit run fix --goal 'fix the off-by-one in pagination'