find-code-simplifications

Find Code Simplifications

Find a few meaningful simplifications with strong evidence. Follow the code and its contracts, keep judgment active, and prefer net reductions in concepts and maintained surface area over cosmetic line-count wins.

Establish The Investigation

1. Determine the requested scope: a branch or PR diff, named modules, or the whole repository.
2. For branch work, establish a fixed comparison base from the user's target, PR metadata, or the verified merge base. Include staged, unstaged, and relevant untracked work when the request covers the current working tree.
3. Read the repository instructions and the architecture, testing, dependency, compatibility, and design-decision documents that govern the selected scope.
4. Inspect the working tree before proceeding and preserve unrelated user changes.
5. Begin read-only. Produce findings first; edit code only when the user explicitly asks for implementation.

Complete this stage when the scope, comparison point, applicable rules, and mutation boundary are explicit.

Identify Strong Candidates

Look for simplifications where the current design costs more than it buys:

• A public method, event, configuration option, helper, package, registry entry, or test artifact has no production consumer.
• Tests or documentation are the only consumers, and the behavior they preserve is not load-bearing.
• Multiple representations, caches, flags, or events mirror the same fact.
• An interface or abstraction forces implementations to support capabilities no production caller uses.
• A wrapper, package, layer, or registry adds indirection without owning policy, state, translation, or lifecycle.
• A feature carries speculative generality for scenarios with no current product or platform owner.
• An invariant, rollback path, expected-output corpus, or special-case test exists only to protect an unused surface.
• Code added and later removed left compatibility branches, configuration, migrations, documentation, snapshots, or tests behind.
• Hand-rolled infrastructure duplicates a standard-library feature or a well-maintained dependency and replacement would produce a real net deletion.
• Similar branches, adapters, commands, or data transformations can share one source of truth without hiding meaningful differences.