Skip to content
SkillModel-led88 tokens in use

Clean Code

Robert C. Martin-inspired rules for readable names, small focused functions and tests that protect behavior.

3,324 stars on the repository MIT Licenseciembor/agent-rules-books · clean-code
npx skills add ciembor/agent-rules-books --skill clean-code
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Clean Code costs

29tokens idle
88tokens in use
3,445tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Needs attention
  • Frontmatter11/15
  • Structure0/25
  • Examples0/15
  • Output2/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity44
  • Maintenance72
  • Community52
  • Maturity28
  • Momentum40

This skill loads a compact rule set inspired by Robert C. Martin’s Clean Code. It tells a coding agent to write for local reasoning: precise names, small functions at one level of abstraction, explicit mutation and a readable happy path.

It is meant as a default for everyday implementation and code review, where working code is only the starting point.

What You Get

  • A mini rule set with decision rules, trigger rules and a closing checklist for everyday coding
  • A nano version for tight context budgets and a full version for reference
  • A skill description that makes the agent load the rules for implementation and review tasks

Common Use Cases

  • Splitting a function that mixes setup, validation, computation and side effects
  • Renaming code whose vocabulary hides intent or forces comments to compensate
  • Separating functions that both mutate state and return answers
  • Reviewing a change for tests that protect the intended contract

What Makes It Unique

It is the smallest and most general of the repository’s rule sets, aimed at daily coding and review without architecture vocabulary. Its checklist ends with questions the agent must answer about its own work, including whether it removed at least one smell and whether it ran the relevant tests. It also limits cleanup to the smallest refactor that makes the requested change safe.

Under The Hood

The skill is a SKILL.md with a name and description, plus Markdown files holding the mini, nano and full versions of the rules. The SKILL.md tells the agent to read the mini file before design or code decisions and the full file only for harder tradeoffs. It contains no scripts. It does not fetch web pages, call APIs, run commands or write files; the agent only reads the rule text.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers