← ClaudeAtlas

clean-codelisted

Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.
Sagargupta16/claude-skills · ★ 3 · Code & Development · score 74
Install: claude install-skill Sagargupta16/claude-skills
# Clean Code (Python) > "Always leave the campground cleaner than you found it." > — Robert Baden-Powell > "Always check a module in cleaner than when you checked it out." > — Robert C. Martin, *Clean Code* ## Rule Chapters Load the chapter that matches the work. Rule IDs (N1, C5, G25, F3, T9...) are defined in these files: | Chapter | When | |---------|------| | [references/full-catalog.md](references/full-catalog.md) | Reviewing any Python -- the complete rule index (master) | | [references/names.md](references/names.md) | Naming variables, functions, classes, modules | | [references/comments.md](references/comments.md) | Writing or editing comments and docstrings | | [references/functions.md](references/functions.md) | Creating or refactoring functions | | [references/general.md](references/general.md) | Code quality review -- DRY, intent, abstractions | | [references/tests.md](references/tests.md) | Writing or reviewing tests | ## The Philosophy You don't have to make every module perfect. You simply have to make it **a little bit better** than when you found it. If we all followed this simple rule: - Our systems would gradually get better as they evolved - Teams would care for the system as a whole - The relentless deterioration of software would end ## When Working on Code Every time you touch code, look for **at least one small improvement**: ### Quick Wins (Do These Immediately) - Rename a poorly named variable → [references/names.md](references/names.md) -