← ClaudeAtlas

overhaullisted

Full-repo overhaul orchestrator: deep refactoring, architecture improvement, dead-code removal, dependency updates, and repo cleanup on any existing project. Use this skill whenever the user asks to "refactor everything", "clean up this repo", "modernize this project", "improve the architecture", "remove dead code", asks for an "overhaul", or activates a frontier model (Fable/Opus) on a legacy or brownfield codebase with broad improvement intent. Also trigger when the user wants to plan work so that a top-tier model architects and cheaper models execute. Works on any git project, any stack.
leonardocandiani/keepwright · ★ 1 · Code & Development · score 67
Install: claude install-skill leonardocandiani/keepwright
# Overhaul Turn a frontier model's limited time into maximum leverage: the strongest model available architects; cheaper models execute. The output of every expensive phase is an **executable artifact** that survives the session, so execution never requires the architect to be present. ## Core contract 1. **Never burn architect time on reconnaissance or mechanical work.** Reconnaissance is fanned out to the cheapest capable model. The architect only reads syntheses and produces plans. 2. **Every phase emits a file.** If a phase's result exists only in conversation, the phase is not done. Artifacts live in `.overhaul/` at the repo root. 3. **All destructive work happens on a dedicated branch** named `overhaul/<yyyy-mm-dd>`. Deletion is aggressive on the branch; the human reviews at the PR. Never commit to the default branch directly. 4. **Empirical proof before merge.** No workstream is complete until its verification command passes (tests, typecheck, build — whatever the plan defines as proof). 5. **The repo must end smarter, not just cleaner.** Lessons learned during execution are catalyzed into rules/validators (see Phase 5). ## Model roles Detect which model is running the current session and slot into the right role. If the session model is the architect-tier model, do Phases 1–2 and STOP — hand off. If it is an executor-tier model given a workstream spec, skip to Phase 4. | Role | Tier (examples) | Does | Never does | |---|---|---|---| |