simplify · fcakyon — скилл для Claude Code: что делает и как установить
Скилл simplify запускает параллельный разбор свежего diff по четырём направлениям и сразу вносит правки для упрощения кода перед коммитом.
Apache-2.0 ★ 1 216 обновлён 2026-11-09
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install simplify@claude-settingsЧто делает simplify
Скилл анализирует изменения в Git через четыре параллельных агента: повторное использование функций, упрощение конструкций, вычислительная эффективность и глубина архитектурного решения. Поиск багов в логике сюда не входит — проверку корректности оставляет для команды /code-review.
Агент собирает diff относительно ветки upstream, PR или рабочих файлов. Он находит дубликаты существующих вспомогательных функций, утечки памяти в замыканиях и лишнюю вложенность, после чего сам вносит правки в код.
Для интеграции с хуками коммита предусмотрен маркер в консоли: если проверку нужно разово пропустить, скилл отдаёт сигнал обхода только по прямому указанию пользователя.
Какие задачи решает
- найти и устранить скрытое дублирование утилит в репозитории
- убрать из diff лишнюю вложенность и мёртвый код
- заменить замыкания с утечками памяти на структуры с копированием полей
- перенести правки из костылей инфраструктуры на правильный уровень абстракции
Примеры запросов агенту
- /simplify
- Упрости изменения в кодовой базе перед коммитом
- Сделай коммит, но пропусти шаг simplify
Как установить simplify
1Через маркетплейс плагинов
/plugin marketplace add fcakyon/claude-codex-settings/plugin install simplify@claude-settingsКоманда ставит плагин simplify целиком, со всеми его скиллами
2Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a claude-code3Вручную: положить файлы
~/.claude/skills/simplify/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/simplify/
1Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a codex2Вручную: положить файлы
.agents/skills/simplify/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a cursor2Вручную: положить файлы
.cursor/skills/simplify/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/simplify/skills/simplify2Вручную: положить файлы
.github/skills/simplify/SKILL.md1Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill simplify -a gemini-cli2Командой платформы
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/simplify/skills/simplifyВручную: положить файлы
.devin/skills/simplify/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Claude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о simplify
Как установить simplify в Claude Code?
Сначала подключите маркетплейс командой /plugin marketplace add fcakyon/claude-codex-settings, а затем выполните /plugin install simplify@claude-settings.
Чем simplify отличается от обычного код-ревью?
Скилл не ищет ошибки реализации и баги бизнес-логики. Его фокус ограничен чистотой diff: повторным использованием готового кода, простотой конструкций и производительностью.
Можно ли пропустить проверку перед коммитом?
Да, для разового обхода хука нужно прямо попросить сделать коммит без шага simplify, после чего в консоль будет отправлен маркер simplify-guard:bypass для текущего worktree.
Исходный текст
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
Похожие скиллы
Все скиллы по теме «Код-ревью и рефакторинг» →Сначала — simplify от других авторов.