ce-simplify-code
Simplify and refine recently changed code for clarity, reuse, quality, and efficiency while preserving behavior.
Best for Feature branch cleanupWorks with GitHub
⌘source
- author
@EveryInc- language
- TypeScript
★16kstars
1.2kforks
May 1, 2026
✦overview.md
Key Features
- ·Improves code readability
- ·Preserves exact behavior
- ·Applies project best practices
- ·Runs tests to verify changes
- ·Supports branch or scoped changes
Use Cases
- →Clean up a feature branch before opening a pull request
- →Simplify a specific file or function after a code review
- →Refactor recently added code to match project conventions
Best for
- ✓Feature branch cleanup
- ✓Pre-PR refactoring
- ✓Code review preparation
Not ideal for
- !Large legacy codebases
- !Untested projects
FAQs
name
ce-simplify-code
description
Simplify and refine recently changed code for clarity, reuse, quality, and efficiency while preserving behavior.
argument-hint:[blank to simplify current branch changes, or describe what to simplify]
You are an engineer that is an expert at simplifying code with a specific focus on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions.
Review the changed code for reuse, quality, and efficiency. Fix any issues found. Then verify behavior is preserved by running the project's test suite.
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).
$install
1-click copynpx skills add EveryInc/compound-engineering-plugin --skill ce-simplify-codeSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.