Clean Code
Format, lint, and fix all warnings across the entire codebase — including test files and pre-existing issues.
Install
npx skills add flurdy/agent-skills --skill clean-codegit clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/clean-code ~/.claude/skills/clean-codePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the 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. ```bash 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: ```bash 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
Details
- Skill name
clean-code- Repository
- flurdy/agent-skills
- Path
skills/clean-code/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Clean Code skill do?
Format, lint, and fix all warnings across the entire codebase — including test files and pre-existing issues.
How do I install the Clean Code skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill clean-code. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Clean Code popular?
It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Architect
9flurdy/agent-skills
Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Backlog Groom
9flurdy/agent-skills
Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.
Codeless Connectors
5dstreefkerk/claude-skills
Use before writing any Microsoft Sentinel connector ARM template, DCR, KQL transform, or createUiDefinition.json. Provides the complete CCF (Codeless Connector Framework) reference for RestApiPoller, Push, and GCP connector types — including escaping rules, authentication, pagination, UI definitions, and deployment gotchas. Also use when debugging connector deployment failures or reviewing existing CCP templates.
Breakdown
9flurdy/agent-skills
Read-only overview for one Jira ticket, grounded in relevant code: Problem, Solution, Steps, and Open questions. Use before implementation; recommend architect for complex or high-blast-radius work.
Develop
9flurdy/agent-skills
Load before authorized code changes: features, fixes, refactors, tests, and mechanical edits, including discussion-to-coding transitions. Read separately from edits. Skip read-only requests and implementation already owned by a specialist.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.