What problem does it solve?
Reads a project's codehealth backlog, selects the highest-priority fixable issues, and orchestrates safe, reviewable fixes without performing direct code edits itself. It removes the manual coordination burden of batching, delegating, and merging quality fixes while preserving project state and approvals.
Core Features & Use Cases
- Backlog-driven fixes: Reads .maestro/quality/backlog.json to pick open high- and medium-severity findings and prioritize quick wins.
- Planned, approved batches: Groups related issues into a batch, documents the approach in .maestro/notes/autofix.md, and presents a product-focused plan for user approval before any code changes.
- Isolated worktrees & delegation: Creates a git worktree for an autofix branch, delegates implementation to sub-agents with strict instructions to operate only in the worktree, reviews results, and merges after verification.
- Progress & safety rails: Writes live status to .maestro/progress/autofix.json, enforces approval gating, uses a merge lock, and never modifies .maestro/state.json.
- Use case: Turn a codehealth scan of error-handling regressions into a single safely-reviewed branch applying 3–7 quick fixes that improve user-facing reliability.
Quick Start
Run the autofix flow to read the codehealth backlog, plan a batch of related quick fixes, present the plan for approval, and apply fixes in an isolated worktree.