ce-simplify-code
Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.
Install
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/ce-simplify-code ~/.claude/skills/ce-simplify-codeFrom README
Step 1: Identify scope Resolve the simplification scope in this order: User-named scope is authoritative; do not widen it. Otherwise, in git, use the current branch versus its base. Without a usable base, use staged and unstaged changes (git diff HEAD). Outside git or without a diff, use files the user named or that were edited earlier in the conversation. If none of the above produces a non-empty scope, stop and ask the user what to simplify rather than guessing. Use the host's blocking question tool already in the current tool list (match by capability, not by a host-specific name). Presence in the current tool list is proof the tool exists; never call a user-facing question tool to discover whether it exists. If a matching tool is listed but unloaded, use the host's tool-discovery primitive to load that capability — do not search for another host's tool name.