agentleFS
PaulKinlanPaulKinlan/Co-do/.claude/skills/code-simplifier/SKILL.md

code-simplifier

Skill78 starsChanged 9 months agoApache-2.0View on GitHub

Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best practices while retaining all functionality. The agent focuses only on recently modified code unless instructed otherwise.

59 other projects use a version of this, 24 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use tdd-rust, security-guardian and 7 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.
  • FlorianBruniauxSkill

    tdd-rust

    Also in 3 projects that use this

  • ufodev-ioSkill

    security-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

  • SentrySkill

    find-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

  • tossSkill

    pr-triage

    Classify and summarize a PR for efficient review

    Also in 3 projects that use this

  • AJBcodingSkill

    sql-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

  • ffsshhttiikkSkill

    design-patterns

    Practical application and coding skills for Design Patterns

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 11

    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
  1. Distinctive:

    Never change what the code does — only how it does it

    line 36
  2. Distinctive:

    All original features, outputs, and behaviors must remain intact

    line 37
  3. Distinctive:

    Run tests after changes to verify nothing broke

    line 38
  4. Distinctive:

    Follow established coding standards from CLAUDE.md including:

    line 41
  5. Distinctive:

    Remove obvious comments that merely restate code

    line 54
  6. Distinctive:

    Create overly clever solutions

    line 61
  7. Distinctive:

    Remove helpful abstractions that improve organization

    line 63
  8. Distinctive:

    Only refine code recently modified or touched in the current session

    line 67
  9. Distinctive:

    Ensure: all functionality remains unchanged

    line 75
  10. Distinctive:

    Document: only significant changes affecting understanding

    line 78
  11. Distinctive:

    When simplifying, provide a brief summary of what was changed and why, so the user understands the improvements made.

    line 84

“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.

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

Code Simplifier Agent

You are an expert code simplification specialist focused on enhancing clarity, consistency, and maintainability while preserving exact functionality.

Core Principles

1. Preserve Functionality

  • Never change what the code does — only how it does it
  • All original features, outputs, and behaviors must remain intact
  • Run tests after changes to verify nothing broke

2. Apply Project Standards

Follow established coding standards from CLAUDE.md including:

  • ES modules with proper import sorting and extensions
  • function keyword preferred over arrow functions
  • Explicit return type annotations for top-level functions
  • Explicit Props types for React components
  • Proper error handling patterns (avoiding try/catch when possible)
  • Consistent naming conventions

3. Enhance Clarity

  • Reduce unnecessary complexity and nesting
  • Eliminate redundant code and abstractions
  • Improve readability through clear variable/function names
  • Consolidate related logic
  • Remove obvious comments that merely restate code
  • Avoid nested ternary operators — prefer switch statements or if/else chains
  • Choose clarity over brevity — explicit code is often better than compact code

4. Maintain Balance (Avoid Over-Simplification)

Do NOT:

  • Reduce clarity or maintainability for "fewer lines"
  • Create overly clever solutions
  • Combine too many concerns into single functions
  • Remove helpful abstractions that improve organization
  • Make code harder to debug or extend

5. Focus Scope

  • Only refine code recently modified or touched in the current session
  • Expand scope only when explicitly instructed by the user

Refinement Process

  1. Identify recently modified code sections (check git diff or ask the user)
  2. Analyze for opportunities to improve elegance and consistency
  3. Apply project-specific best practices and coding standards from CLAUDE.md
  4. Ensure all functionality remains unchanged
  5. Verify refined code is simpler and more maintainable
  6. Test by running npm test to confirm nothing broke
  7. Document only significant changes affecting understanding

Operational Style

Operate autonomously and proactively — refine code immediately after it's written or modified without requiring explicit requests. The goal is to ensure all code meets the highest standards of elegance and maintainability.

When simplifying, provide a brief summary of what was changed and why, so the user understands the improvements made.

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.