agentleFS
Sign inStart free
flurdyflurdy/agent-skills/skills/clean-code/SKILL.md

clean-code

Skill9 starsChanged 3 months agoMITView on GitHub

Format, lint, and fix all warnings across the entire codebase — including test files and pre-existing issues.

108 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, nextjs-react-expert and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 5 projects that use this

  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • xfstudioSkill

    bash-pro

    Master of defensive Bash scripting for production automation, CI/CD

    Also in 4 projects that use this

  • xfstudioSkill

    code-refactoring-tech-debt

    You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

    Also in 4 projects that use this

  • flying-diceSkill

    clean-code-review

    Multi-agent clean code audit — each principle gets its own agent

    Also in 3 projects that use this

  • goca-seSkill

    batch-operations

    Apply a change safely across many files — refactors touching more than 5 files, library or API migrations, project-wide renames of symbols/imports/paths, or adding boilerplate to many files. Use when "do it all at once" risks context overflow or silent failures.

    Also in 3 projects that use this

  • +4 more from xfstudio

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 101 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If make clean-code fails or reports warnings/errors that couldn't be auto-fixed, investigate and fix them manually.

    line 34
  2. Very specific:

    Do not skip or suppress warnings (e.g.

    line 48
  3. Distinctive:

    Do not change the project's formatter or linter configuration

    line 49
  4. Distinctive:

    If a fix changes behavior (not just style), flag it to the user before applying

    line 50
  5. Distinctive:

    Test files are in scope — do not skip them

    line 51

“Common” is measured: kept by at least 6 in 10 of the 101 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Clean Code

Format, lint, and fix all warnings across the entire codebase — including test files and pre-existing issues.

Usage

/clean-code

Instructions

1. Run the project's clean-code target

Each project defines a make clean-code Makefile target with the appropriate tooling for its language/stack.

make clean-code

2. Fix remaining issues

If make clean-code fails or reports warnings/errors that couldn't be auto-fixed, investigate and fix them manually. Do NOT leave any warnings unresolved.

3. Verify clean state

Re-run the target to confirm it passes cleanly:

make clean-code

It must exit with zero warnings and zero errors.

Rules

  • Do not skip or suppress warnings (e.g. eslint-disable, #[allow(...)], @SuppressWarnings) unless there is a genuine false positive with a clear justification
  • Do not change the project's formatter or linter configuration
  • If a fix changes behavior (not just style), flag it to the user before applying
  • Test files are in scope — do not skip them
  • Pre-existing issues must be fixed, not just new code

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free