ce-simplify-code
Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; 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
Mode Strip a mode:pipeline token and every proof-test: token from the input before reading the rest as the scope. The proof-test path is context for Step 3, never scope; a caller may pass several. Pipeline when mode:pipeline is present, or when no one asked for this run in their own current message: a step of another skill, or a run the agent starts itself, such as at a completion boundary. Work only on the current work, apply fixes without asking or waiting, and return the Step 5 summary to the caller. That summary is for the caller's record; never paste it into a commit, PR body, or other artifact. Standalone when the user's own current message asked for this run. Their request sets the scope and focus. Report findings before editing anything, unless the request says to just fix them. Read references/standalone-report.md now, and again before applying any reported finding. Step 1: Identify scope Resolve the scope in this order: User-named scope is authoritative; do not widen it.
More from this repo
ce-brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only unified plan.
ce-code-review
Used to review a named diff or PR for bugs, regressions, tests, and standards.
ce-commit
Used to create a git commit with a clear, value-communicating message.