omgskills Get the Mac app
Skill

ce-simplify-code

@everyinc 23k stars Updated 2026-07-24 Author match: High

Simplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use ce-debug for bugs.

compoundengineering

Install

Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.

Install command
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-code

View on GitHub

From README

Step 1: Identify scope Resolve the simplification scope in this order: If the user explicitly named a scope (a file, a directory, "the function I just wrote", "the changes from this morning"), use that scope. Treat user-named scope as authoritative — do not widen it. Otherwise, in a git repository, default to the diff between the current branch and its base branch (e.g., git diff origin/main... or against the configured upstream). This covers the common case of "simplify everything I've added on this feature branch before opening a PR." If the branch has no upstream or base ref, fall back to staged + unstaged changes (git diff HEAD). Outside a git repository or when no diff is available, review the most recently modified files mentioned by the user or edited earlier in this conversation. If none of the above produces a non-empty scope, stop and ask the user what to simplify rather than guessing.

More from this repo