agentleFS
Sign inStart free
sampleXbrosampleXbro/agentsmesh/.agents/skills/am-command-code-simplify/SKILL.md

am-command-code-simplify

Skill27 starsChanged 2 months agoMITView on GitHub

Simplify code for clarity and maintainability — reduce complexity without changing behavior

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

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

    Read CLAUDE.md and study project conventions

    line 12
  2. Distinctive:

    Verify all tests pass, the build succeeds, and the diff is clean

    line 23
  3. Very specific:

    If tests fail after a simplification, revert that change and reconsider.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Invoke the agent-skills:code-simplification skill.

Simplify recently changed code (or the specified scope) while preserving exact behavior:

  1. Read CLAUDE.md and study project conventions
  2. Identify the target code — recent changes unless a broader scope is specified
  3. Understand the code's purpose, callers, edge cases, and test coverage before touching it
  4. Scan for simplification opportunities:
    • Deep nesting → guard clauses or extracted helpers
    • Long functions → split by responsibility
    • Nested ternaries → if/else or switch
    • Generic names → descriptive names
    • Duplicated logic → shared functions
    • Dead code → remove after confirming
  5. Apply each simplification incrementally — run tests after each change
  6. Verify all tests pass, the build succeeds, and the diff is clean

If tests fail after a simplification, revert that change and reconsider. Use code-review-and-quality to review the result.

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.

Check your setup, free