← ClaudeAtlas

clean-codebaselisted

Use when a codebase of any language or size has drifted: scattered duplicate logic, tangled module dependencies, layers that hide related code, a backlog of one-off special cases, or changes that break in places nobody can see from the code. Untangles the project so agents working in it read less per change, break less without noticing, and debug faster.
titanxdevz/clean-codebase · ★ 1 · Code & Development · score 77
Install: claude install-skill titanxdevz/clean-codebase
# Untangle a codebase Start a thorough refactor of this codebase and complete it to the end. Treat this as a goal. **Why do this at all?** - **Better output:** agents write better code in a well-structured codebase. - **Cheaper and faster changes:** agents spend fewer tokens searching and more on the problem. - **Fewer silent breaks:** agents break less without noticing. - **Faster debugging:** agents find root causes faster. The core question, asked of every boundary in the project: **should these pieces change together?** A good boundary answers yes for the pieces that share a reason to change, and no for everything else. This skill finds the boundaries where the code answers wrongly, then moves code until the answer is right. Nothing here is specific to a language or a build system. The method is the same for a 400-line Python script and a 400,000-line Java monorepo; only the commands change. ## When to use this, and when not to Use it when the codebase has drifted: duplicated logic in several places, modules that import each other in a cycle, a feature split across layer folders so that one change needs four directories, a growing pile of `if` branches that each handle exactly one situation, or wrappers and config options nothing ever varies. Do not use it when: - The change is small enough to make directly. A two-file cleanup does not need a structural redesign. - The project is mid-incident and the priority is stability, not structure. - The build is already b