clean-code
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
- Version
- 1.4.0
- License
- MIT
Pinned to revision 4f7124e6049e, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/clean-code/SKILL.md
- skills/clean-code/references/code-smells.md
- skills/clean-code/references/comments-formatting.md
- skills/clean-code/references/error-handling.md
- skills/clean-code/references/functions-and-methods.md
- skills/clean-code/references/naming-conventions.md
- skills/clean-code/references/testing-principles.md
Every link opens the file at its source, pinned to the revision this page describes.