remove-dead-code

To safely remove dead code, create a timestamped backup branch from HEAD first, then scan the project to generate a reviewable report before proceeding with any removals.

Static analysis can detect dead code in projects with complex dependencies including dynamic imports and guarded exports, using parallel agents to cross-check and confirm dead code before removal.

The best way to clean up unused JavaScript is a conservative approach that keeps code when in doubt, requiring multi-agent validation and post-removal verification to protect live functionality.

Dead code removal works across codebases with complex dependencies including test utilities, but it conservatively preserves public API surfaces to avoid accidentally removing live functionality.

The dead code refactoring process requires a backup branch to protect the original state before any modification, ensuring you can restore the codebase if post-removal verification fails.

You should not use automated dead code removal when you cannot create a backup branch first, or when your project heavily relies on dynamic imports that static analysis cannot fully trace.