clean
/clean
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one.
- Author
- anilsoylu ↗
- Repository
- famiglia ↗
- Licence
- Apache-2.0
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one.
Triggers from the description
Original author description
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one.
How it works
- Do
- Don't
SKILL.md preview
--- name: clean description: >- Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one. --- # Clean KISS/DRY and copy the local code style. Be elitist, shorthand, clever, concise, efficient, and elegant. **"Clean" means polishing the code — it does NOT mean running the test suite, tsc, or lint as the task.** Run a check only if it's genuinely needed to confirm the polish is safe. Clean is a standalone pass, not just a pre-PR step — run it whenever things get messy, including mid-work. Also run it automatically before any PR handoff (creating, updating, automerging, or moving to the next PR) without being told each time. ## Do 1. Re-read your diff. Cut dead code, leftover debug logging, and duplication. 2. Extend existing helpers — don't parallel-implement. 3. Match neighboring style (names, imports, file layout, comment density). 4. Prefer the small sharp version over ceremony. 5. UI work: only after they like the UI (`ui-only`). Use `ui-system` for primitives. 6. On the PR: title/body describe the change as a whole (a short intro), not a changelog of steps. Split into topical commits (`pr-update`), run `no-tropes` on the text, and link the PR. ## Don't - Run the test suite / tsc / lint just because you were told to "clean" - Unrelated refactors - New abstractions with one caller - Scope creep dressed up as cleanup
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · anilsoylu/famiglia | 90 | Apache-2.0 |
| lucastamoios/skills | 100 | MIT |
| kurtosis-tech/kurtosis | 95 | Apache-2.0 |
| nazmirket/skills | 90 | MIT |
| bkhtmm/cLEAN | 90 | MIT |
| melodic-software/claude-code-plugins | 84 | MIT |
Database snapshot: 13.11.2026 · package version fa12c6ae3b6a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100clean-code
Coding standards (SRP, DRY, KISS, YAGNI, naming) with a pre-edit dependency check and a completion self-check. Use when writing, editing or finishing code. - 100clean-code-principles
SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. Use when reviewing architecture, checking code quality, refactoring, or discussing design decisions. Triggers on "review architecture", "check code quality", "SOLID principles", "design patterns", or "clean code". - 95clean-code
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead. - 100react-principles
Principles and practices for writing React: SOLID, DRY/KISS/YAGNI, Hooks, state, effects, TypeScript and testing. Use when creating, refactoring or reviewing React components, Hooks, props or frontend structure. - 100clean-code-guard
Review generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing,… - 80Code Standards
This skill should be used when the user asks about "code quality", "file size limits", "function length", "KISS", "DRY", "YAGNI", "SRP", "best practices", "clean code", "cyclomatic complexity", "code review checklist", "refactoring rules", or mentions specific thresholds for…