Dead Code Detection

Overview

Dead code detection identifies code that exists in your codebase but is never called, imported, or used. This is a critical signal for incomplete feature integration: if you've written a function but nothing calls it, the feature isn't wired up.

In loom plan verification, dead code checks serve two purposes:

1. Wiring verification: Catch features that were implemented but never integrated
2. Code quality: Identify cleanup opportunities and reduce maintenance burden

Dead code detection is especially valuable in integration-verify stages, where it acts as a final check that all implemented code is actually connected to the application.

When to Use

• integration-verify stages: Final quality gate to catch orphaned code from all implementation stages
• Per-stage acceptance criteria: Immediate feedback during implementation
• Code cleanup: After refactoring or feature removal
• Wiring validation: Combine with wiring checks to verify feature integration