domains / families / software-engineering / clean-code

clean-code

combined

Apply Robert C. Martin-inspired clean code rules when improving readability, naming, function design, responsibilities, or testable everyday code. This skill embodies the principles of \"Clean Code\" by Robert C. Martin (Uncle Bob). Use it to transform \"code that works\" into \"code that is clean.\"

When to use

• **Writing new code**: To ensure high quality from the start.
• **Reviewing Pull Requests**: To provide constructive, principle-based feedback.
• **Refactoring legacy code**: To identify and remove code smells.
• **Improving team standards**: To align on industry-standard best practices.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies overlap on the core Clean Code principles (naming, small functions, comments, formatting, error handling, tests), but each contains material steps or constraints the others lack. wondelai/skills adds a 0-10 scoring rubric, a Boy Scout Rule framing, and references to deeper per-topic files. ciembor/agent-rules-books is a thin router that mandates reading a mini rules file before a deeper reference, a workflow constraint absent from the others. sickn33/agentic-awesome-skills adds explicit sections for Objects/Data Structures (Law of Demeter, DTOs), Classes, Smells and Heuristics, an implementation checklist, and a limitations block. Crowning one copy would hide the scoring rubric, the mini-file workflow, and the additional structural/smell sections, so the copies should be combined.