simplify · fcakyon — Claude Code skill: what it does, how to install
simplify runs four parallel agents to inspect and clean up recent diffs across reuse, complexity, and performance before committing.
Apache-2.0 ★ 1,216 updated 2026-11-09
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install simplify@claude-settingsWhat simplify does
The skill reviews pending Git changes across four distinct dimensions: helper reuse, state simplification, runtime overhead, and architectural altitude. It leaves logic and correctness bugs to /code-review, concentrating strictly on maintainability and structural bloat.
Diffs are gathered from upstream branches, commits, or uncommitted files. Each agent flags deep nesting, dead code, duplicated utilities, or closures holding heavy scope references, then the skill directly applies the deduped refactorings.
When pre-commit hooks guard the workflow, the skill emits an exact completion or bypass marker tied to the active worktree, but skips review only upon an explicit skip request.
What it helps with
- clean up uncommitted diffs before creating a commit
- deduplicate utility functions already present in the codebase
- flatten deeply nested logic and drop dead code
- prevent memory leaks caused by closures capturing large scopes
Example prompts for the agent
- /simplify
- clean up the diff before making a commit
- commit this but skip simplify
How to install simplify
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install simplify@claude-settingsThis installs the whole simplify plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a claude-code3Manually: put the files in place
~/.claude/skills/simplify/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/simplify/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a codex2Manually: put the files in place
.agents/skills/simplify/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a cursor2Manually: put the files in place
.cursor/skills/simplify/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/simplify/skills/simplify2Manually: put the files in place
.github/skills/simplify/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/simplify/skills/simplifyManually: put the files in place
.devin/skills/simplify/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about simplify
How to install simplify in Claude Code?
Add the repository with /plugin marketplace add fcakyon/claude-codex-settings, then install the package by running /plugin install simplify@claude-settings.
Does simplify search for application bugs?
No, it intentionally avoids checking for correctness bugs. Its sole purpose is cleaning diffs, reducing complexity, and improving code reuse.
Can you bypass the review for a quick commit?
Yes, if you explicitly ask to commit without simplify, it sends a single-use bypass signal to the worktree hook without disabling --no-verify.
Source text
SKILL.md · Apache-2.0
---
name: simplify
description: This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code across reuse, simplification, efficiency, and altitude, or grants an explicit one-commit bypass. Not for correctness bugs.
---
# Simplify
`/simplify → 4 cleanup agents in parallel → apply the fixes`
You are improving the quality of the changed code, not hunting for bugs. Review it for reuse, simplification, efficiency, and altitude issues, then fix what you find. Do not look for correctness bugs, that is what `/code-review` is for.
## Explicit commit bypass
If the user explicitly asks to commit while skipping simplify, skip the review phases below:
1. State that simplify will be skipped for one commit and normal Git hooks will still run.
2. Resolve the worktree you will commit in with `git -C '<worktree>' rev-parse --show-toplevel`. In a separate shell invocation, run this exact command by itself with that absolute path:
```bash
echo simplify-guard:bypass '/absolute/path/to/worktree'
```
The hook recognizes only the standalone `echo` signal. Run `git commit` in a later invocation. The marker is tied to that worktree and is consumed by one commit attempt.
3. Commit normally without `--no-verify`.
Never infer permission to bypass from the size, urgency, or type of change. The user must explicitly name simplify when asking to skip it.
## Phase 0 — Gather the diff
Run `git diff @{upstream}...HEAD` (or `git diff main...HEAD` / `git diff HEAD~1` if there's no upstream) to get the unified diff under review. If there are uncommitted changes, or the range diff is empty, also run `git diff HEAD` and include the working-tree changes in scope, the review often runs before the commit. If a PR number, branch name, or file path was passed as an argument, review that target instead. Treat this diff as the review scope.
## Phase 1 — Review (4 cleanup agents in parallel)
Run **4 distinct reviews**, one for each angle below. Launch four independent agents concurrently when capacity allows. If fewer than four slots are available, run the remaining angles in later waves, never in the primary agent. Never omit or combine an angle. Pass each agent the diff and its assigned angle. Each returns its findings with `file`, `line`, a one-line `summary`, and the concrete cost (what is duplicated, wasted, or harder to maintain).
### Reuse
Flag new code that re-implements something the codebase already has. Grep shared/utility modules and files adjacent to the change, and name the existing helper to call instead.
### Simplification
Flag unnecessary complexity the diff adds: redundant or derivable state, copy-paste with slight variation, deep nesting, dead code left behind. Name the simpler form that does the same job.
### Efficiency
Flag wasted work the diff introduces: redundant computation or repeated I/O, independent operations run sequentially, blocking work added to startup or hot paths. Also flag long-lived objects built from closures or captured environments, they keep the entire enclosing scope alive for the object's lifetime (a memory leak when that scope holds large values). Prefer a class/struct that copies only the fields it needs. Name the cheaper alternative.
### Altitude
Check that each change is implemented at the right depth, not as a fragile bandaid. Special cases layered on shared infrastructure are a sign the fix isn't deep enough, prefer generalizing the underlying mechanism over adding special cases.
## Phase 2 — Apply the fixes
Wait for all four agents to complete, dedup findings that point at the same line or mechanism, and fix each remaining one directly. Skip any finding whose fix would change intended behavior, require changes well outside the reviewed diff, or that you judge to be a false positive, note the skip rather than arguing with it.
## Phase 3: Mark completion
After all accepted fixes are applied, resolve the reviewed worktree with `git -C '<reviewed-worktree>' rev-parse --show-toplevel`. In a separate shell invocation, run this exact command by itself with that absolute path:
```bash
echo simplify-guard:complete '/absolute/path/to/reviewed/worktree'
```
This lets the bundled guard record completion against the reviewed worktree even when the session started elsewhere. The hook recognizes only the standalone `echo` signal. Run the commit in a later invocation. The marker is one-use and belongs to the worktree's Git directory. If a commit attempt is denied, verify the review is still current and send the standalone completion command again before retrying.
Finish with a brief summary of what was fixed and what was skipped (or confirm the code was already clean).
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings
Similar skills
All skills for Code review and refactoring →simplify by other authors comes first.