Menu
Behavior-preserving cleanup pass over recently-changed code. Invoked by review-and-simplify after the review lenses, before a commit is proposed.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | simplify |
| description | Behavior-preserving cleanup pass over recently-changed code. Invoked by review-and-simplify after the review lenses, before a commit is proposed. |
When: invoked by review-and-simplify after the review lenses are clean, before any commit is proposed. MANDATORY step in that orchestration — not a standalone judgment call to skip.
Scope: ONLY the recently-changed code — the feature's diff. Never the whole repo unless the human explicitly asks for a broader pass.
Preserve functionality EXACTLY — change how the code reads, never what it does. This is a readability pass, not a refactor of behavior. If a change you're considering could alter an observable input/output, a side effect, or an edge case, it does not belong here.
Apply the project's CLAUDE.md code style (function length, naming, no any, comment-WHY-not-WHAT) while doing this pass.
data/handler/Manager-style placeholders).if/else or switch.Do not over-simplify:
.specify/gates/run-gates.sh and the project's tests. Confirm everything is STILL green and output is pristine — this is the proof that behavior was preserved, not just an assumption.This skill edits code, then verifies. It is not a blocking review — code-review and security-review are the read-only lenses; this is the one step in the chain that's allowed to touch the diff.
Next: if simplify changed non-trivial logic shape (not just naming/formatting), review-and-simplify re-runs the relevant lens before the pre-commit gate.
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.