Dead Code Eliminator

Use this skill when the user wants a dead-code audit, not a broad refactor. The default outcome is a reachability report and a removal order, with code changes only after the audit is clear.

Main Workflow

1. Find the project entry points: executables, CLI bins, routes, jobs, exports, package indexes, and framework lifecycle hooks.
2. Trace the live set from those roots through imports, calls, instantiations, and other statically provable edges.
3. Mark anything unresolved, conditional, or externally consumable instead of guessing reachability.
4. Separate test-only reachability from production reachability.
5. Report dead code candidates, confidence level, and any correctness or soundness concerns in the live code.
6. If the user asks for removal, delete in dependency-safe order after the audit is complete.

Safety Rules

• Do not guess through reflection, eval, string dispatch, or other dynamic lookup paths.
• Treat feature-flagged or environment-conditional code as conditionally reachable and name the condition.
• Treat symbols that may be consumed outside the repository as unused export (external consumers possible), not as dead code.
• Do not collapse low-confidence items into the dead list without calling out the uncertainty.