code-simplifier

Code Simplifier

Simplify only the relevant changed code unless the user explicitly asks for a broader sweep. Preserve behavior, outputs, error semantics, side effects, and public interfaces.

Default to a single-agent simplification pass. Use spawn_agent only when the user explicitly asks for delegation, parallel subagents, or a multi-agent review and the touched scope is broad enough to benefit.

Workflow

1. Identify the scope.

• Prefer the files or hunks changed in the current task.
• If the scope is unclear, inspect the named function, file, or recent diff.
• Avoid unrelated cleanup outside the touched area.

1. Read the project's local conventions.

• Check AGENTS.md, nearby code, formatter and lint rules, and type patterns.
• Match the repository's style instead of forcing a generic one.
• Reuse existing helpers before introducing new abstractions or dependencies.

1. Decide whether to delegate.

• Keep the immediate blocking work local. Form a short plan before spawning anything.
• Do not delegate small, tightly coupled, or urgent blocking work where your next step depends on the answer.
• If the user explicitly asks for parallelism and the work is broad enough, use spawn_agent for bounded subtasks that can run in parallel with your local work.
• Prefer narrow prompts and explicit file or symbol scope over copying the full thread context. Use fork_context only when the subagent truly needs the same conversation history.
• Prefer explorer agents for read-heavy simplification analysis. Reserve worker agents for implementation only when the write scope can be split into disjoint files or modules.

1. Review the code through three simplification lenses.

• Reuse: prefer existing helpers, utilities, and local patterns before adding new abstractions; remove duplication when the shared shape is stable.
• Quality: improve readability, naming, branching, cohesion, and type clarity; preserve logging, validation, and error semantics.
• Efficiency: remove unnecessary work in the touched code such as redundant passes, allocations, awaits, or lookups when the improvement is obvious and behavior stays identical.
• If the lenses conflict, prefer behavioral safety and readability over extra DRYing or micro-optimizations.