Simplifying Code

Principles

Process

1. Read first -- understand the full file and its dependents before changing anything. Apply Chesterton's Fence: if you see code that looks unnecessary but don't understand why it's there, check git blame before removing it. First understand the reason, then decide if the reason still applies.
2. Identify invariants -- what must stay the same? Public API, return types, side effects, error behavior
3. Identify targets -- find the highest-impact simplification opportunities. Impact = readability and maintainability; prioritize: control flow -> naming -> duplication -> types (see Smell -> Fix table)
4. Apply in order -- control flow → naming → duplication → data shaping → types. Structural changes first, cosmetic last
5. Verify -- confirm no behavior change: tests pass, types check, imports resolve
6. Pre-submit scope audit -- walk every changed line and ask "does the requested task explicitly require this line?" If no, revert it and list it as a follow-up under Residual Risks. Drive-by edits belong in a separate change, not the current patch. For the pre-edit complement on ambiguous-scope requests ("simplify my project"), see ia-verification-before-completion's Scope Confirmation gate.

Smell → Fix

AI Slop Removal

When simplifying AI-generated code, specifically target:

• Redundant comments that restate the code (// increment counter above counter++) -- delete them
• Unnecessary defensive checks for conditions that cannot occur in context -- remove the guard
• Gratuitous type casts (as any, as unknown as T) -- fix the actual type or use a proper generic
• Over-abstraction (factory for 2 objects, wrapper around a single call, util file with 1 function) -- inline the code
• Inconsistent style that drifts from the file's existing conventions -- match the file
• Placeholder stubs (// ..., // rest of code, // similar to above, // continue pattern, // add more as needed) -- leave unsimplified code as-is rather than replacing it with stubs
• Redundant error wrapping (catch(e) { throw e; }, catch(e) { throw new Error(e.message); }) that strips the original stack for no reason -- remove the try/catch entirely and let errors propagate
• Verbose stdlib reimplementations (hand-rolled loops that replicate array_filter, Array.from, Collection::pluck(), itertools) -- replace with the stdlib/framework one-liner

Stop Conditions

Stop and ask before proceeding when:

• Simplification requires changing a public API (function signatures, return types, exports)
• Behavior parity cannot be verified (no tests exist and behavior is non-obvious)
• Code is intentionally complex for domain reasons (performance-critical, protocol compliance)
• Scope implies a redesign rather than a simplification

Constraints

• Only simplify what was requested -- do not add features, expand scope, or introduce new dependencies
• Leave unchanged code untouched -- do not add comments, docstrings, or type annotations to lines that were not simplified
• Do not bundle unrelated cleanups into one patch -- each simplification should be a coherent, reviewable unit
• Do not introduce framework-wide patterns while simplifying a small local change
• Do not replace understandable duplication with opaque utility layers -- three similar lines are better than a premature abstraction
• Keep comments that explain intent, invariants, or non-obvious constraints. Remove comments that restate obvious code behavior.
• If a simplification would make the code harder to understand, skip it
• Watch for over-simplification: inlining too aggressively removes names that gave concepts meaning; combining unrelated logic into one function hides distinct responsibilities; removing abstractions that exist for testability breaks the test suite
• When unsure whether a block is dead code, ask instead of deleting

Verify

• Tests pass and types check after changes
• No behavior change (same inputs produce same outputs)
• Scope limited to requested files -- no drive-by cleanups

Orchestrator Mode (When Chained With Other Skills)

When this skill is invoked by an orchestrator that also runs ia-code-review, ia-writing-tests, or ia-verification-before-completion on the same scope, each sub-skill re-resolving scope independently wastes tokens and risks drift. Avoid this by resolving scope exactly once and passing a canonical block to every sub-skill.

Resolved scope format — the orchestrator builds this once, before dispatching any sub-skill:

## Resolved scope
Files:
- path/to/file-a.ts
- path/to/file-b.ts

Commit range: HEAD~3..HEAD (or "uncommitted")

Intent: [one-sentence description pulled from the user request or PR description]

Constraints:
- Preserve public API
- No behavior change
- [other constraints specific to this run]

Every chained sub-skill receives this block verbatim in its prompt and uses it as the source of truth — no re-running git diff --name-only, no re-parsing the user request, no independent scope resolution. Sub-skills accept --no-verify --no-report flags when chained so verification and reporting happen once at the end of the chain, not per-skill. The last sub-skill in the chain runs verification; the orchestrator trusts that result rather than re-verifying.

This prevents two failure modes: scope drift (sub-skill A simplifies one set of files, sub-skill B reviews a different set) and double work (every sub-skill rediscovers the same facts).

Integration

• ia-code-simplicity-reviewer agent -- analysis-only pass producing a simplification report (no code changes). Use before refactoring to identify targets.

Output

After simplifying, report:

• Scope touched: files and functions modified
• Key simplifications: what changed and why (one line each)
• Verification: tests pass, types check, no behavior change
• Residual risks: assumptions made, areas not touched that may need attention