Codebase Simplify

Run a read-only, whole-repository simplification audit. Return findings in the conversation; leave repository and external state unchanged.

Read Simplification Signals before surveying the code.

1. Map The Repository

Read the effective repository instructions, architecture docs, manifests, production entry points, and current git status. Define the production corpus, evidence corpus such as tests and docs, and intentional exclusions such as generated or vendored code.

Partition the production corpus into review areas along existing runtime, workspace, or module seams. Record each area's paths and entry points in a coverage map.

Completion criterion: every production path belongs to one review area or an explicit exclusion, and the starting HEAD and worktree state are known.

2. Survey Broadly

Inspect every review area against the simplification signals. Start with the largest production surfaces and the code with the most states, interfaces, lifecycle machinery, or cross-module coordination; symbol-level dead-code searches are supporting evidence, not the survey boundary.

For repositories with independent areas, assign disjoint areas to parallel sub-agents when available. Require each survey to report its coverage, candidates, and areas examined without a candidate.