clean-code

Apply Clean Code refactoring by making functions small and single-purpose, using intention-revealing names, removing redundant comments, and keeping one level of abstraction per function. The Skill provides a checklist covering function size, naming, arguments, and tests.

Review code by checking naming clarity, function length under 20 lines, single responsibility per function, minimal arguments, and absence of side effects. The Skill structures feedback around these principle-based criteria for pull requests.

Functions should be small, do exactly one thing, maintain one level of abstraction, and take zero to two arguments ideally. They should have descriptive verb names and avoid hidden side effects on global state.

Avoid applying it when the task does not match the described scope, or when environment-specific validation and testing are required. The Skill is guidance, not a substitute for expert review, so ask for clarification if success criteria are unclear.

Yes, it includes the Three Laws of TDD and the F.I.R.S.T. principles: tests should be Fast, Independent, Repeatable, Self-Validating, and Timely. Write a failing test before writing production code.