code-simplifier
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
59 other projects use a version of this, 27 of them edited.
Adopted by
Most recently taken up by
- euxx/claude-skills-for-copilotedited, first seen Nov 8, 2026
- aktsmm/Agent-Skillsedited, 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/skillsedited, 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 9 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
PaulKinlanSkillcomment-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
tossSkillpr-triage
Classify and summarize a PR for efficient review
Also in 3 projects that use this
AJBcodingSkillsql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
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 · 27
- tisfeng/Easydict★ 15k15% same
- getsentry/skills★ 1.1k99% same
- deadlock-mod-manager/deadlock-mod-manager★ 58499% same
- taskless/cli★ 14195% same
- keep-starknet-strange/starkzap★ 10813% same
- PaulKinlan/Co-do★ 7821% same
- zvadaadam/az-skills★ 5075% same
- roman01la/skills-agents★ 4899% same
- fanqingxuan/awesome-skills★ 2850% same
- aktsmm/Agent-Skills★ 2618% same
17 more not listed
Wrote their own version · 32
- rtk-ai/rtk★ 86ksame name
- elie222/inbox-zero★ 13ksame name
- Azure/azqr★ 799same name
- DoubleML/doubleml-for-py★ 798same name
- microsoft/ghqr★ 528same name
- feiskyer/codex-settings★ 248same name
- wesm/middleman★ 198same name
- OpenHands/extensions★ 167same name
- FlorianBruniaux/ccboard★ 94same name
- 1024XEngineer/bytemind★ 43same name
22 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 repository110 other files it gives its agents.
- acquire-codebase-knowledgeSkill
- add-educational-commentsSkill
- agnes-blog-postSkill
- algorithmic-artSkill
- api-and-interface-designSkill
- api-breaking-change-detectorSkill
- api-setupSkill
- architecture-blueprint-generatorSkill
- baoyu-article-illustratorSkill
- baoyu-cover-imageSkill
- baoyu-diagramSkill
- baoyu-format-markdownSkill
- baoyu-infographicSkill
- baoyu-markdown-to-htmlSkill
- baoyu-slide-deckSkill
- baoyu-translateSkill
- baoyu-xhs-imagesSkill
- baoyu-youtube-transcriptSkill
- beadsSkill
- blog-writing-guideSkill
- breakdown-feature-prdSkill
- browser-automationSkill
- canvas-designSkill
- chat-with-pdfSkill
- code-review-and-qualitySkill
- code-reviewSkill
- code-simplificationSkill
- code-tourSkill
- cold-emailSkill
- commitSkill
- company-researchSkill
- competitive-analysisSkill
- context-engineeringSkill
- conventional-commitSkill
- convert-excel-to-mdSkill
- convert-word-to-mdSkill
- copy-editingSkill
- create-architectural-decision-recordSkill
- create-branchSkill
- create-videoSkill
- critical-code-reviewerSkill
- data-analysisSkill
- data-reportSkill
- debugging-and-error-recoverySkill
- deep-researchSkill
- deprecation-and-migrationSkill
- diagram-creatorSkill
- diagram-designSkill
- discernment-nudgeSkill
- distillySkill
- documentation-and-adrsSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- ecommerce-visual-copywritingSkill
- file-organizerSkill
- find-bugsSkill
- finishing-a-development-branchSkill
- frontend-designSkill
- gh-address-commentsSkill
- git-guardrails-claude-codeSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 13 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 51
Never change what the code does - only how it does it.
- Distinctive: line 55
Follow the established coding standards from CLAUDE.md including:
- Distinctive: line 57
Use ES modules with proper import sorting and extensions
- Very specific: line 58
Prefer function keyword over arrow functions
- Distinctive: line 59
Use explicit return type annotations for top-level functions
- Distinctive: line 60
Follow proper React component patterns with explicit Props types
- Distinctive: line 61
Use proper error handling patterns (avoid try/catch when possible)
- Distinctive: line 73
Avoiding nested ternary operators: - prefer switch statements or if/else chains for multiple conditions
- Distinctive: line 78
Avoid over-simplification that could:
- Distinctive: line 81
Create overly clever solutions that are hard to understand
- Distinctive: line 83
Remove helpful abstractions that improve code organization
- Distinctive: line 89
Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.
- Distinctive: line 96
Ensure: all functionality remains unchanged
- Distinctive: line 98
Document: only significant changes that affect understanding
“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
<!--
Based on Anthropic's code-simplifier agent:
https://github.com/anthropics/claude-plugins-official/blob/main/plugins/code-simplifier/agents/code-simplifier.md
-->Code Simplifier
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions.
Refinement Principles
1. Preserve Functionality
Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.
2. Apply Project Standards
Follow the established coding standards from CLAUDE.md including:
- Use ES modules with proper import sorting and extensions
- Prefer
functionkeyword over arrow functions - Use explicit return type annotations for top-level functions
- Follow proper React component patterns with explicit Props types
- Use proper error handling patterns (avoid try/catch when possible)
- Maintain consistent naming conventions
3. Enhance Clarity
Simplify code structure by:
- Reducing unnecessary complexity and nesting
- Eliminating redundant code and abstractions
- Improving readability through clear variable and function names
- Consolidating related logic
- Removing unnecessary comments that describe obvious code
- Avoiding nested ternary operators - prefer switch statements or if/else chains for multiple conditions
- Choosing clarity over brevity - explicit code is often better than overly compact code
4. Maintain Balance
Avoid over-simplification that could:
- Reduce code clarity or maintainability
- Create overly clever solutions that are hard to understand
- Combine too many concerns into single functions or components
- Remove helpful abstractions that improve code organization
- Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners)
- Make the code harder to debug or extend
5. Focus Scope
Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.
Refinement Process
- Identify the recently modified code sections
- Analyze for opportunities to improve elegance and consistency
- Apply project-specific best practices and coding standards
- Ensure all functionality remains unchanged
- Verify the refined code is simpler and more maintainable
- Document only significant changes that affect understanding
Examples
Before: Nested Ternaries
const status = isLoading ? 'loading' : hasError ? 'error' : isComplete ? 'complete' : 'idle';After: Clear Switch Statement
function getStatus(isLoading: boolean, hasError: boolean, isComplete: boolean): string {
if (isLoading) return 'loading';
if (hasError) return 'error';
if (isComplete) return 'complete';
return 'idle';
}Before: Overly Compact
const result = arr.filter(x => x > 0).map(x => x * 2).reduce((a, b) => a + b, 0);After: Clear Steps
const positiveNumbers = arr.filter(x => x > 0);
const doubled = positiveNumbers.map(x => x * 2);
const sum = doubled.reduce((a, b) => a + b, 0);Before: Redundant Abstraction
function isNotEmpty(arr: unknown[]): boolean {
return arr.length > 0;
}
if (isNotEmpty(items)) {
// ...
}After: Direct Check
if (items.length > 0) {
// ...
}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.

