code-simplifier
Skill1 starsChanged 7 months agoApache-2.0View on GitHub
Use this skill after completing code changes to review for reuse, quality, and efficiency. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.
59 other projects use a version of this.
Adopted by
Most recently taken up by
- euxx/claude-skills-for-copilottheir own version, first seen Nov 8, 2026
- aktsmm/Agent-Skillstheir own version, first seen Nov 8, 2026
- ValorVie/custom-skillstheir own version, first seen Nov 8, 2026
- ZhouYinLong-lab/Dog-Skillstheir own version, first seen Nov 8, 2026
- simonwong/skillstheir own version, first seen Nov 6, 2026
- islandhopper81/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use tdd-rust, type-design-analyzer 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.
FlorianBruniauxSkilltdd-rust
Also in 3 projects that use this
PaulKinlanSkilltype-design-analyzer
Analyzes type design quality focusing on encapsulation, invariant expression, usefulness, and enforcement. Provides quantitative ratings (1-10) for each dimension.
Also in 3 projects that use this
- PaulKinlanSkill
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps.
Also in 4 projects that use this
ufodev-ioSkillsecurity-guardian
Comprehensive security layer for all interactions with Claude: audits code, dependencies, commands, configs, and AI-generated output for vulnerabilities. Protects against prompt injection, data leaks, unsafe advice, and social engineering. Works in Cursor, Claude Code, claude.ai, and API contexts. Use always as a background security protocol in any Claude-powered environment.
Also in 3 projects that use this
SentrySkillfind-bugs
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
Also in 3 projects that use this
tossSkillpr-triage
Classify and summarize a PR for efficient review
Also in 3 projects that use this
- +1 more from PaulKinlan
Other versions59 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 59
- rtk-ai/rtk★ 86ksame name
- tisfeng/Easydict★ 15ksame name
- elie222/inbox-zero★ 13ksame name
- getsentry/skills★ 1.1ksame name
- Azure/azqr★ 799same name
- DoubleML/doubleml-for-py★ 798same name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- microsoft/ghqr★ 528same name
- feiskyer/codex-settings★ 248same name
- wesm/middleman★ 198same name
49 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- code-reviewSkill
- coding-workflowSkill
- commit-push-prSkill
- data-analystSkill
- data-triageSkill
- data-workflowSkill
- pr-descriptionSkill
- repo-skillsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
After completing code changes, review your work for opportunities to simplify and improve.
- Distinctive: line 37
Keep changes minimal and focused: only simplify, do not add features or refactor beyond what's needed
- Distinctive: line 42
Do not refactor unrelated code
“Common” is measured: kept by at least 6 in 10 of the 54 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.
Files
Code Simplifier
After completing code changes, review your work for opportunities to simplify and improve.
What to Check
Reuse
- Are there existing utilities, helpers, or patterns in the codebase that do the same thing?
- Did you duplicate logic that already exists elsewhere?
- Can any new helpers be consolidated with existing ones?
Quality
- Is the code consistent with surrounding patterns and conventions?
- Are variable/function names clear and descriptive?
- Is control flow straightforward? Flatten nested conditionals with guard clauses and early returns.
- Are there unnecessary abstractions or over-engineering?
- Is error handling appropriate — not too much, not too little?
Efficiency
- Are there redundant operations (duplicate API calls, repeated computations, unnecessary loops)?
- Could any logic be simplified with built-in language features or standard library tools?
- Are imports clean and minimal?
Process
- Review all files you modified in this session
- For each file, check against the criteria above
- Fix any issues found — do not just flag them
- Keep changes minimal and focused: only simplify, do not add features or refactor beyond what's needed
Scope
- Focus on code you wrote or modified in this session
- Do not refactor unrelated code
- Preserve all existing functionality — simplification must not change behavior
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
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.