/simplify

Reviews changed code for cleanup opportunities (reuse, simplification, efficiency) and applies the fixes directly, without hunting for correctness bugs.

[Skill] Four review agents run in parallel: reuse, simplification, efficiency, abstraction level. From v2.1.154, no bug hunting (use /code-review for that). A path or PR reference can be given as the target.

✅ WHEN TO USE IT?

Clean up after a finished feature

Once a feature already works and is tested, run /simplify on the changed code to improve reuse, simplification, and efficiency.

Clean up one path without bug hunting

Call /simplify src/utils/parser.ts to clean up just that file without also hunting for correctness bugs.

⛔ WHEN NOT TO?

Bugs need to be found too

Per the docs, since v2.1.154 /simplify explicitly no longer hunts for correctness bugs, only cleanup potential.

Better: Use /code-review, which also covers correctness bugs.

SOURCES

Claude Code Doku (offiziell) ↗ code.claude.com