Dead Code Hunter

Scan this repository for dead code - unused files, functions, classes, variables, and exports. Generate a comprehensive report and safe deletion patch.

Analysis Steps

1. Identify Entry Points

   • Find main/index files, package.json scripts, exports
   • Map public API surface

2. Scan for Unused Code

   • Functions/methods never called
   • Classes never instantiated
   • Variables declared but never read
   • Files not imported anywhere
   • Exports never consumed
   • Dead branches (unreachable code)

3. Verify Safety

   • Check for dynamic imports/requires
   • Look for reflection or metaprogramming
   • Identify test files (don't flag test-only usage as dead)
   • Check for CLI entry points
   • Look for framework magic (decorators, lifecycle hooks)

Output Format

Dead Code Report

Create a markdown report with:

# Dead Code Analysis Report

## Summary
- Total files scanned: X
- Potentially unused files: X
- Potentially unused functions: X
- Estimated removable lines: X

## High Confidence (Safe to Remove)
Items with no references found anywhere:
- [ ] `path/to/file.ts` - entire file unused
- [ ] `src/utils.ts:functionName` (lines 45-67)

## Medium Confidence (Review Recommended)
Items that might have dynamic usage:
- [ ] `path/to/file.ts:export` - only used in tests

## Low Confidence (Investigate)
Items with potential indirect usage:
- [ ] `src/api.ts:handler` - might be route handler

Git Patch

After the report, generate a git patch file that can be applied with git apply:

diff --git a/path/to/unused-file.ts b/path/to/unused-file.ts
deleted file mode 100644
--- a/path/to/unused-file.ts
+++ /dev/null
@@ -1,XX +0,0 @@
-[file contents]

Save the patch to dead-code-removal.patch in the project root.

Important

• Be conservative - false positives waste developer time
• Group related dead code (if a file is dead, don't also list its functions)
• Explain WHY each item appears unused
• Never flag framework-required files (configs, manifests)