cleanup
Cleanup
Run only after an explicit cleanup request. Discussing, implementing, or reviewing this skill does not invoke it. If loaded without a cleanup request, return to the user's task without starting a sweep.
Own a bounded repository sweep from discovery through verification. By default, fix clear issues that preserve behavior and discuss larger changes. Honor a request for findings only. This skill works on its own and does not require code, Git, subagents, or another installed skill.
Establish the scope
- Identify the target repository or requested areas, the user's goals, and any focus, exclusions, or resource limits. Ask about consequential unknowns; use the existing context for settled choices.
- Read applicable project instructions and entry points. Map the relevant source, tests, documentation, configuration, tooling, and their boundaries. Follow the existing organization unless a change solves a concrete problem.
- Inspect the current work when available. Preserve unrelated edits, untracked files, and user data; their presence does not make them cleanup candidates.
- Identify useful existing checks and record relevant baseline failures when practical. Avoid checks with unapproved effects. If execution or file access is limited, continue with the accessible evidence and state the limits.
- Use a plan or coverage record at the scale the work needs. The conversation can hold it; a broad or interrupted sweep may benefit from an existing project record. Do not require a new report, tracker, branch, or worktree.
Without writable files, return findings and proposed edits as text and state that nothing was saved.
A full sweep covers the relevant authored areas of the repository. Generated output, vendored code, external repositories, and ignored or sensitive material are normally excluded unless the request and project context make them relevant. Record what was inspected, sampled, or skipped, with meaningful limits. A targeted request narrows the sweep to its named areas or concerns.