Cyclomatic Complexity
saurabhkumar8112/cyclomatic-complexity-skill
Refactor code to reduce cyclomatic complexity so it stays readable, maintainable, and aligned with the long-term vision of the codebase, not just optimized for AI comprehension.
A skill your agent uses when writing, reviewing, or refactoring code for maintainability and readability.
Install Clean Code
$ npx skills add pproenca/dot-skills --skill clean-code -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills clean-code --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/clean-code .claude/skills/clean-code && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "clean-code" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code into .claude/skills/clean-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-codeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill clean-code -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills clean-code --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/clean-code .agents/skills/clean-code && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clean-code" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code into .agents/skills/clean-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill clean-code -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills clean-code --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/clean-code .cursor/skills/clean-code && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clean-code" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code into .cursor/skills/clean-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/clean-code--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill clean-code -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills clean-code --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/clean-code .gemini/skills/clean-code && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clean-code" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code into .gemini/skills/clean-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills clean-codeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill clean-code -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/clean-code .github/skills/clean-code && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clean-code" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code into .github/skills/clean-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill clean-code -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills clean-code --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/clean-code .opencode/skills/clean-code && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clean-code" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/clean-code into .opencode/skills/clean-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-code", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
clean-code- GitHub stars
- 214
- Token cost
- ~1.8k tokens
- SKILL.md length
- 495 words
- Files
- 52 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing, reviewing, or refactoring code for maintainability and readability.
- Works in 10 steps: Meaningful Names (CRITICAL) → Functions (CRITICAL) → Comments (HIGH) → …
- Refactoring code for maintainability and readability
- SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clean Code is an agent skill from pproenca/dot-skills. Use when writing, reviewing, or refactoring code for maintainability and readability. Triggers on code reviews, naming discussions, function design, error handling, and test writing. Based on Robert C. Martin's Clean Code handbook with modern corrections.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 54 other files, including reference files and assets (for example `assets/templates/_template.md`, `metadata.json` and `references/_sections.md`).
It sits in Development, covering Code quality, Code review and Plain language and style rules. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Refactoring code for maintainability and readability
- Naming discussions
- Function design
Example prompts
- “/clean-code”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Clean Code loads about 1.8k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 495 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 495 words, ~1,760 tokens.
Download SKILL.mdSave it as
.claude/skills/clean-code/SKILL.md (or your agent's skills folder). This skill also uses 51 other files; get the full folder from GitHub.- name
- clean-code
- description
- Use when writing, reviewing, or refactoring code for maintainability and readability. Triggers on code reviews, naming discussions, function design, error handling, and test writing. Based on Robert C. Martin's Clean Code handbook with modern corrections.
Robert C. Martin (Uncle Bob) Clean Code Best Practices
Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.
When to Apply
Reference these guidelines when:
- Writing new functions, classes, or modules
- Naming variables, functions, classes, or files
- Reviewing code for maintainability issues
- Refactoring existing code to improve clarity
- Writing or improving unit tests
- Wrapping third-party dependencies
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Meaningful Names | CRITICAL | name- |
| 2 | Functions | CRITICAL | func- |
| 3 | Comments | HIGH | cmt- |
| 4 | Formatting | HIGH | fmt- |
| 5 | Error Handling | HIGH | err- |
| 6 | Objects and Data Structures | MEDIUM-HIGH | obj- |
| 7 | Boundaries | MEDIUM-HIGH | bound- |
| 8 | Classes and Systems | MEDIUM-HIGH | class- |
| 9 | Unit Tests | MEDIUM | test- |
| 10 | Emergence and Simple Design | MEDIUM | emerge- |
Quick Reference
1. Meaningful Names (CRITICAL)
name-intention-revealing- Use names that reveal intentname-avoid-disinformation- Avoid misleading namesname-meaningful-distinctions- Make meaningful distinctionsname-pronounceable- Use pronounceable namesname-searchable- Use searchable namesname-avoid-encodings- Avoid encodings in namesname-class-noun- Use noun phrases for class namesname-method-verb- Use verb phrases for method names
2. Functions (CRITICAL)
func-small- Keep functions smallfunc-one-thing- Functions should do one thingfunc-abstraction-level- Maintain one level of abstractionfunc-minimize-arguments- Minimize function argumentsfunc-no-side-effects- Avoid side effectsfunc-command-query-separation- Separate commands from queriesfunc-dry- Do not repeat yourself
3. Comments (HIGH)
cmt-express-in-code- Express yourself in code, not commentscmt-explain-intent- Use comments to explain intentcmt-avoid-redundant- Avoid redundant commentscmt-avoid-commented-out-code- Delete commented-out codecmt-warning-consequences- Use warning comments for consequences
4. Formatting (HIGH)
fmt-vertical-formatting- Use vertical formatting for readabilityfmt-horizontal-alignment- Avoid horizontal alignmentfmt-team-rules- Follow team formatting rulesfmt-indentation- Respect indentation rules
Show full SKILL.md (197 more words)Show less
5. Error Handling (HIGH)
err-use-exceptions- Separate error handling from happy patherr-write-try-catch-first- Write try-catch-finally firsterr-provide-context- Provide context with exceptionserr-define-by-caller-needs- Define exceptions by caller needserr-avoid-null- Avoid returning and passing null
6. Objects and Data Structures (MEDIUM-HIGH)
obj-data-abstraction- Hide data behind abstractionsobj-data-object-asymmetry- Understand data/object anti-symmetryobj-law-of-demeter- Follow the Law of Demeterobj-avoid-hybrids- Avoid hybrid data-object structuresobj-dto- Use DTOs for data transfer
7. Boundaries (MEDIUM-HIGH)
bound-wrap-third-party- Wrap third-party APIsbound-learning-tests- Write learning tests for third-party code
8. Classes and Systems (MEDIUM-HIGH)
class-small- Keep classes smallclass-cohesion- Maintain class cohesionclass-organize-for-change- Organize classes for changeclass-isolate-from-change- Isolate classes from changeclass-separate-concerns- Separate construction from use
9. Unit Tests (MEDIUM)
test-first-law- Follow the three laws of TDDtest-keep-clean- Keep tests cleantest-one-assert- One concept per testtest-first-principles- Follow FIRST principlestest-build-operate-check- Use Build-Operate-Check pattern
10. Emergence and Simple Design (MEDIUM)
emerge-simple-design- Follow the four rules of simple designemerge-expressiveness- Maximize expressiveness
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 51 other files (references, assets) in skills/.experimental/clean-code of pproenca/dot-skills.
- SKILL.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/bound-learning-tests.md
- references/bound-wrap-third-party.md
- references/class-cohesion.md
- references/class-isolate-from-change.md
- references/class-organize-for-change.md
- references/class-separate-concerns.md
- references/class-small.md
- references/cmt-avoid-commented-out-code.md
- references/cmt-avoid-redundant.md
- references/cmt-explain-intent.md
- references/cmt-express-in-code.md
- references/cmt-warning-consequences.md
- references/emerge-expressiveness.md
- references/emerge-simple-design.md
- … and 34 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Clean Code next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clean Code this skillpproenca/dot-skills | 214 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Cyclomatic Complexitysaurabhkumar8112/cyclomatic-complexity-skill | 405 | — | ~761 | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewhardness1020/Leeway | 115 | — | ~301 | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Skill Doli Code ReviewDolibarr/dolibarr | 7.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Dignified Python Standardsdocling-project/docling | 68k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Code Review
hardness1020/Leeway
Code quality review — identify patterns, anti-patterns, and improvements.
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Skill Doli Code Review
Dolibarr/dolibarr
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
Dignified Python Standards
docling-project/docling
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
Clean Code Guard
amElnagdy/guard-skills
Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Categories
Questions about Clean Code
What does Clean Code do?
A skill your agent uses when writing, reviewing, or refactoring code for maintainability and readability. Clean Code is an agent skill from pproenca/dot-skills. Use when writing, reviewing, or refactoring code for maintainability and readability.
When should I use Clean Code?
Clean Code fits situations like: refactoring code for maintainability and readability; naming discussions; function design.
How do I install Clean Code in Claude Code?
Run `npx skills add pproenca/dot-skills --skill clean-code -a claude-code`. Or copy the skill folder (skills/.experimental/clean-code in pproenca/dot-skills) into .claude/skills/clean-code in your project. Claude Code loads it when a task matches its description.
How do I install Clean Code in Codex?
Run `npx skills add pproenca/dot-skills --skill clean-code -a codex`. Or copy the skill folder (skills/.experimental/clean-code in pproenca/dot-skills) into .agents/skills/clean-code in your project. Codex loads it when a task matches its description.
Can I use Clean Code in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill clean-code -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean-code, .gemini/skills/clean-code, .github/skills/clean-code and .opencode/skills/clean-code in your project.
What does Clean Code need to run?
SKILL.md names no scripts, command-line tools or credentials: Clean Code is instructions for the agent only.
Does Clean Code access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Clean Code safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Clean Code use?
Clean Code is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clean Code use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 24k tokens, read only when the agent opens those files.
What are the alternatives to Clean Code?
Skills that share tags, products or a category with Clean Code: Cyclomatic Complexity (saurabhkumar8112/cyclomatic-complexity-skill, 405 stars), Code Review (hardness1020/Leeway, 115 stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars) and Skill Doli Code Review (Dolibarr/dolibarr, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clean Code?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.