Menu

Individual skill

code-simplifier

Simplify existing code for clarity and maintainability without changing behavior. Use when asked to clean up or simplify code, especially recent changes.

skills/code-simplifier/SKILL.md

Read pinned source

Source commit d7f65709e64c2b959bfe84cf8a33d56907f76636

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
248
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Code Simplifier

Make code easier to understand and maintain without changing what it does. Prefer readable, explicit code over compact or clever rewrites.

## Scope and conventions

Use the user's named files or diff. Otherwise, focus on code touched in the current task or clearly identified recent changes; ask for a target if none is evident. Inspect surrounding code as needed without turning a local cleanup into a repository-wide refactor. For review-only requests, propose changes without editing.

Follow applicable project guidance, such as `AGENTS.md` or `CLAUDE.md`, and the conventions in nearby code. Derive import style, function syntax, type annotations, framework patterns, and error handling from that project rather than imposing a different style.

## Refinement criteria

- Preserve observable behavior, including public interfaces, outputs, errors, side effects, and evaluation order. Treat bug fixes or behavior changes as separate work unless requested.
- Reduce unnecessary nesting, duplication, and indirection where doing so makes the logic easier to follow. Keep helpful abstractions and separate unrelated concerns.