Dead Code Cleanup: Find Unreachable Paths Without Guessing

Dead code cleanup is safest when it starts from reachability, not suspicion. A file can look unused because it is loaded through a registry, imported by a plugin, generated at build time, or only executed by a rare repair command.

The useful output is a dead-code removal pull request with static references, dynamic-loader checks, test output, and rollback notes. Keep the review concrete: Remove call sites or registrations before deleting the implementation, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when deleting code that is loaded dynamically.

Key takeaways

Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
Use one release cycle plus the longest supported client or repair-command window before deciding that “quiet” means “unused.”
Prefer reversible changes first when deleting code that is loaded dynamically is still plausible.
Leave behind a dead-code removal pull request with static references, dynamic-loader checks, test output, and rollback notes so the next review starts with context.
Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.

Trace Reachability First

Start with one package, module boundary, or service surface where imports, runtime logs, build targets, and release branches can be checked together. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	owners, callers, last change, runtime behavior, and deletion confidence
Dependency evidence	repository search, tests, logs, deploy history, and owner review
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Evidence Beyond Text Search

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For dead code cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Static references	Imports, exports, route registration, package entry points, and generated code	No normal build path points at the candidate
Dynamic loading	Plugin registries, reflection, config-driven imports, templates, and command dispatch	No indirect loader can still reach the code
Runtime proof	Logs, tracing spans, coverage from production-like tests, and error reports	Supported traffic and jobs do not execute the path
Consumer contract	Public API docs, old release branches, SDK consumers, and migration notes	No supported consumer relies on the old behavior

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Example Evidence Check

Pair ordinary text search with registry and command discovery so dynamically loaded paths are not missed.

rg "OldImporter|legacyExport|repairCustomerState" src tests scripts
rg "register|plugin|command|handler|loader" src config
rg "OldImporter|legacyExport" docs runbooks .github

Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.

Delete One Path at a Time

Use the least permanent move that proves the decision. In dead code cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

Remove call sites or registrations before deleting the implementation.
Run the build targets and tests that exercise optional plugins, workers, and release commands.
Delete one dependency path at a time so a bad assumption has a small revert.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Code That Only Looks Dead

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Plugin hooks, reflection, code generation, and config-selected modules.
Repair tools, migration commands, and incident-only paths that do not appear in daily traffic.
Compatibility layers used by older clients or long-lived release branches.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the Removal Pull Request

Run dead code cleanup as a decision review, not an open-ended hygiene project.

Pick the narrow scope and export the candidate list.
Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
Apply the least permanent useful change first.
Watch the signals that would reveal a bad decision.
Complete the final removal only after the review window closes.
Save a dead-code removal pull request with static references, dynamic-loader checks, test output, and rollback notes.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Make Deprecation Visible

Prevention should change the creation path, not just the cleanup path. For dead code cleanup, the useful prevention fields are owner, reason to exist, removal trigger, and verification notes. Make those fields part of normal creation and review.

Require new extension points to register owners and supported callers.
Add reachability or dependency checks to CI where the language ecosystem supports them.
Treat deprecated paths as queued removals with dates, not as permanent comments.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Unreachable code in application codebases
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Static references, Dynamic loading, and owner confirmation
First reversible move	Remove call sites or registrations before deleting the implementation
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after one release cycle plus the longest supported client or repair-command window
Prevention rule	Require new extension points to register owners and supported callers

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do dead code cleanup?

Use one release cycle plus the longest supported client or repair-command window for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, remove call sites or registrations before deleting the implementation. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to plugin hooks, reflection, code generation, and config-selected modules. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.