Cleanup Project

Get a repository to a clean foundation before new work: every uncommitted change decided, ignore files updated, merged branches deleted locally and on origin, and an up-to-date, clean main.

When to use

• "Clean up this repo before I start the next feature."
• "Delete the branches that are already merged, local and remote."
• "My working tree is a mess. Help me decide what to keep and get back to main."
• "Tidy the .gitignore and get rid of stale branches."
• "Is spike/llm-cache worth keeping?" This goes straight to the single-branch drill-down (Step 6).

Don't use it to remove dead code or unused imports (code-review mode:cleanup), commit and push everything (auto-push), cut a release or tag (ship), or add LICENSE, CONTRIBUTING and other OSS files (oss-ready). For a git how-to question ("branch -d vs -D?"), answer it directly and run no workflow.

Inputs