Clean Code
Apply Clean Code principles by Robert C. Martin (Uncle Bob) when writing new code, refactoring existing code, or reviewing changes in any language. Covers meaningful names, small functions, comments, formatting, objects vs data structures, error handling, boundaries, unit tests, classes, systems, emergent design, concurrency, and code smells.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill clean-codegit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/clean-code ~/.claude/skills/clean-codePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Clean Code (Robert C. Martin) Apply these principles whenever writing, refactoring, or reviewing code. Code is read far more often than it is written — optimize for the reader, not the writer. ## Core Philosophy - **The Boy Scout Rule**: Leave the code cleaner than you found it. - **Bad code rots**: small disciplines compound; small messes compound faster. - **Clean code does one thing well**, reads like prose, contains no duplication, and minimizes the number of moving parts. - **Care is the missing ingredient**. Clean code is a result of attention, not talent. --- ## Chapter 2: Meaningful Names **Use intention-revealing names.** The name must answer: why it exists, what it does, how it is used. If you need a comment to explain a name, the name has failed. ```csharp // Bad int d; // elapsed time in days // Good int elapsedTimeInDays; ``` **Avoid disinformation.** Don't call something a `List` if it isn't one. Don't use `l` and `O` as variable names (they look like `1` and `0`). **Make meaningful distinctions.** `a1`, `a2`, `Info`, `Data`, `Object`, `Variable`, `theMessage` vs `message` — these are noise. If two names exist, they must mean different things. **Use pronounceable names.** `genymdhms` is unspeakable in code review; `generationTimestamp` is. **Use searchable names.** Single letters only inside short loop bodies. `MAX_CLASSES_PER_STUDENT` is grep-able; the literal `7` is not.
Details
- Skill name
clean-code- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/clean-code/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Clean Code skill do?
Apply Clean Code principles by Robert C. Martin (Uncle Bob) when writing new code, refactoring existing code, or reviewing changes in any language. Covers meaningful names, small functions, comments, formatting, objects vs data structures, error handling, boundaries, unit tests, classes, systems, emergent design, concurrency, and code smells.
How do I install the Clean Code skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Clean Code popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Code Review
8Freddy-CHEN-ux/00_claude_skills
Use for quick self-review of small changes. For comprehensive review or cross-domain changes, dispatch @code-reviewer agent instead.
Claude Code Skills
8Freddy-CHEN-ux/00_claude_skills
Comprehensive reference for creating Claude Code skills with progressive disclosure, SKILL.md structure, resources/ organization, frontmatter specification, and best practices for modular capability development.
Codebase Conventions
8Freddy-CHEN-ux/00_claude_skills
Load when starting work in 10x-Mapmaster or when unsure about project standards. Covers file organization, naming conventions, type constraints, SQL style, and project-specific limits (200-char descriptions, answer enums). Use to understand how the codebase is structured and what standards to follow.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.