Use when writing or reviewing functions, classes, naming, or non-trivial logic (≥3 lines).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Writing Clean Code
## Overview
**Code is read far more often than it is written, so optimize the artifact for the next reader.** This skill is a small set of decisions to apply when you write a new function, name a new entity, or touch a non-trivial block of logic. Each decision pairs with a check a reviewer (human or agent) could apply by reading the diff.
## When to invoke
Invoke when you're about to:
- Add a new function, method, class, struct, or module
- Name a new entity that other code will reference (variable, function, type, file)
- Modify ≥3 lines of non-trivial logic — branching, loops, conditional dispatch, or anything that reads as "behavior" rather than "wiring"
- Add or replace a comment block of more than one line
- Copy-paste a block of logic from elsewhere in the codebase
- Review code for readability, naming, duplication, or structural quality
If you're unsure whether the change is non-trivial, ask: *would a reviewer pause on this hunk to think about it?* If yes, invoke.
### Non-triggers — do NOT invoke for
- Typo fixes or one-line bug fixes where the change is obvious
- Config edits — JSON, YAML, TOML, dotfiles, lock files, env files
…
The line at the top of this page pins the label git:20260510.17c5ab8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (9722 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
oribarilan/97 · 25 stars · license a license file GitHub does not identify · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_penjsblye432krem
GET https://markdownregistry.com/api/v1/resolve?ref=oribarilan/97/clean-code
GET https://markdownregistry.com/api/v1/blob/3bf2599c01a2ae4dce0025ef1563598b9d9e415db8128887f617026a206da132
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
oribarilan/97 · skills/api-design/SKILL.md · Use when designing or reviewing a public API, exported function signature, module boundary, exported type/interface, or…
oribarilan/97 · skills/before-you-refactor/SKILL.md · Use when considering, evaluating, or performing a refactor, restructure, cross-file rename, or cleanup
oribarilan/97 · skills/build-deploy-and-tooling/SKILL.md · Use when writing, reviewing, or changing build scripts, CI workflows, deploy pipelines, repo setup, or evaluating a new…
oribarilan/97 · skills/domain-modeling/SKILL.md · Use when introducing, reviewing, or renaming a top-level type, table, or domain concept; or choosing where state lives…
oribarilan/97 · skills/observability/SKILL.md · Use when writing or reviewing request handlers, RPCs, or background jobs for production; adding tracing, metrics, or…
oribarilan/97 · skills/security-and-trust-boundaries/SKILL.md · Use when writing or reviewing code that parses user input, builds SQL/shell commands, handles secrets/credentials…
oribarilan/97 · skills/self-review/SKILL.md · Use when about to commit, finish a task, open a PR, summarize work for the user, or when the user asks for a review or…
oribarilan/97 · skills/testing-discipline/SKILL.md · Use when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test…
oribarilan/97 · skills/working-with-users-and-team/SKILL.md · Use when gathering or interpreting requirements, estimating effort, or communicating with stakeholders/customers about…
ciembor/agent-rules-books · clean-code/SKILL.md · Apply Robert C. Martin-inspired clean code rules when improving readability, naming, function design, responsibilities…
wondelai/skills · plugins/code-craftsmanship/skills/clean-code/SKILL.md · Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the…
wondelai/skills · clean-code/SKILL.md · Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the…
wondelai/skills · plugins/wondelai-skills/skills/clean-code/SKILL.md · Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the…
decebals/claude-code-java · skills/clean-code/SKILL.md · Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with…
asymmetric-al/core · .agents/skills/clean-code/SKILL.md · Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to…
