How do I install the Clean Code skill?

Run npx skillmds@latest add tomevault-io/clean-code-5 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clean Code safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clean Code?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clean Code free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clean Code?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clean Code by tomevault-io — Agent Skill

Name: Clean Code
Author: tomevault-io

Clean Code

Clean Code principles and practices reference based on Robert Martin's work. Use this skill when reviewing code quality, naming conventions, refactoring, or applying SOLID principles. Auto-activates for code smell detection, style improvements, and maintainability concerns. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Clean Code Reference

A comprehensive reference for writing clean, maintainable code based on Robert Martin's "Clean Code" and related works. This skill provides language-agnostic principles with examples that apply to any programming language.

When This Skill Activates

This skill automatically activates when you:

Review code for quality or maintainability
Need guidance on naming conventions
Discuss refactoring or code smells
Apply SOLID principles
Improve code readability or structure
Write or review unit tests

Quick Reference

SOLID Principles

Principle	Summary	Violation Sign
Single Responsibility (SRP)	One reason to change	Class does too many things
Open/Closed (OCP)	Open for extension, closed for modification	Modifying existing code for new features
Liskov Substitution (LSP)	Subtypes must be substitutable	Subclass breaks parent behavior
Interface Segregation (ISP)	No forced dependencies on unused methods	Fat interfaces
Dependency Inversion (DIP)	Depend on abstractions, not concretions	High-level modules import low-level

Clean Code Practices

Practice	Key Points
Meaningful Names	Intention-revealing, pronounceable, searchable
Functions	Small, do one thing, one level of abstraction
Comments	Code should be self-documenting; comments explain why, not what
Formatting	Consistent style, vertical density, horizontal alignment
Error Handling	Exceptions over error codes, fail fast, don't return null
Unit Testing	F.I.R.S.T. principles, one assert per test, test behavior
Code Smells	Recognition and refactoring of common problems
Boy Scout Rule	Leave code cleaner than you found it

The Boy Scout Rule

"Leave the campground cleaner than you found it."

Every time you touch code, make it a little better. Small, incremental improvements compound over time.

Code Quality Checklist

Before committing code, verify:

Names - Are all names intention-revealing?
Functions - Is each function doing exactly one thing?
Comments - Are comments explaining why, not what?
DRY - Is there any duplicated logic?
SOLID - Are principles being followed?
Tests - Is the code tested and testable?
Error Handling - Are errors handled gracefully?

Language Translation Notes

Examples use generic pseudocode. Adapt to your language:

PHP: class, function, ->, type hints
JavaScript/TypeScript: class, arrow functions, .
Python: class, def, ., type hints
Java/C#: Direct mapping with access modifiers

Based on concepts from "Clean Code: A Handbook of Agile Software Craftsmanship" by Robert C. Martin, 2008.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: clean-code-5description: Clean Code principles and practices reference based on Robert Martin's work. Use this skill when reviewing code quality, naming conventions, refactoring, or applying SOLID principles. Auto-activates for code smell detection, style improvements, and maintainability concerns. Use when this capability is needed.---# Clean Code ReferenceA comprehensive reference for writing clean, maintainable code based on Robert Martin's "Clean Code" and related works. This skill provides language-agnostic principles with examples that apply to any programming language.## When This Skill ActivatesThis skill automatically activates when you:- Review code for quality or maintainability- Need guidance on naming conventions- Discuss refactoring or code smells- Apply SOLID principles- Improve code readability or structure- Write or review unit tests## Quick Reference### SOLID Principles| Principle | Summary | Violation Sign ||-----------|---------|----------------|| [Single Responsibility (SRP)](solid/single-responsibility.md) | One reason to change | Class does too many things || [Open/Closed (OCP)](solid/open-closed.md) | Open for extension, closed for modification | Modifying existing code for new features || [Liskov Substitution (LSP)](solid/liskov-substitution.md) | Subtypes must be substitutable | Subclass breaks parent behavior || [Interface Segregation (ISP)](solid/interface-segregation.md) | No forced dependencies on unused methods | Fat interfaces || [Dependency Inversion (DIP)](solid/dependency-inversion.md) | Depend on abstractions, not concretions | High-level modules import low-level |### Clean Code Practices| Practice | Key Points ||----------|------------|| [Meaningful Names](practices/meaningful-names.md) | Intention-revealing, pronounceable, searchable || [Functions](practices/functions.md) | Small, do one thing, one level of abstraction || [Comments](practices/comments.md) | Code should be self-documenting; comments explain why, not what || [Formatting](practices/formatting.md) | Consistent style, vertical density, horizontal alignment || [Error Handling](practices/error-handling.md) | Exceptions over error codes, fail fast, don't return null || [Unit Testing](practices/unit-testing.md) | F.I.R.S.T. principles, one assert per test, test behavior || [Code Smells](practices/code-smells.md) | Recognition and refactoring of common problems || [Boy Scout Rule](practices/boy-scout-rule.md) | Leave code cleaner than you found it |## The Boy Scout Rule> "Leave the campground cleaner than you found it."Every time you touch code, make it a little better. Small, incremental improvements compound over time.## Code Quality ChecklistBefore committing code, verify:- [ ] **Names** - Are all names intention-revealing?- [ ] **Functions** - Is each function doing exactly one thing?- [ ] **Comments** - Are comments explaining why, not what?- [ ] **DRY** - Is there any duplicated logic?- [ ] **SOLID** - Are principles being followed?- [ ] **Tests** - Is the code tested and testable?- [ ] **Error Handling** - Are errors handled gracefully?## Language Translation NotesExamples use generic pseudocode. Adapt to your language:- **PHP**: `class`, `function`, `->`, type hints- **JavaScript/TypeScript**: `class`, arrow functions, `.`- **Python**: `class`, `def`, `.`, type hints- **Java/C#**: Direct mapping with access modifiers---*Based on concepts from "Clean Code: A Handbook of Agile Software Craftsmanship" by Robert C. Martin, 2008.*---> Converted and distributed by [TomeVault](https://tomevault.io/claim/grndlvl) — claim your Tome and manage your conversions.

Frequently asked questions