Clean Code
pproenca/dot-skillsWriting clean code makes your software easier to understand and change. This guide follows the famous advice of Robert C. Martin, also known as Uncle Bob. It covers 48 rules for naming, functions, comments, and more. These rules help developers write code that is simple and clear.
You can use these rules when reviewing code, naming things, or writing tests. They help you avoid common mistakes and keep your codebase healthy. The guide is organized by priority, so you know which practices matter most.
Whether you are a beginner or an expert, these best practices will improve your coding skills. They apply to any programming language and any project.
Add Clean Code skill to your workflow
Global
mkdir -p ~/.claude/skills/clean-codeProject
mkdir -p .claude/skills/clean-codeSource Repository
More Code Review & Quality Claude Code Skills
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective