Clean Code Skill

Iron Law: Before applying any principle, READ the relevant source file first. Do not refactor or flag issues based on memory — verify the actual code (file:line) before making any claim.

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."

Core Philosophy

"Code is clean if it can be read, and enhanced by a developer other than its original author." — Grady Booch

When to Use

• Writing new code: Ensure high quality from the start.
• Reviewing Pull Requests: Provide constructive, principle-based feedback.
• Refactoring legacy code: Identify and remove code smells.
• Improving team standards: Align on industry-standard best practices.