dead-code

Dead code detection locates unreferenced private or internal symbols across a loaded Roslyn-based workspace, verifies their usage with reference checks, and safely removes them after a preview. It preserves behavior by ensuring conservative changes with compile checks.

Safe dead code cleanup uses a deterministic preview and apply workflow with compile checks. The audit verifies references before any removal to prevent regressions, applying changes only after explicit user confirmation.

Yes, the dead code audit can optionally scope to a specific project when provided. This allows you to target static analysis and cleanup efforts at a subset of the loaded Roslyn workspace.

Dead code detection safeguards public APIs by preserving them unless explicitly overridden. It focuses on locating unreferenced private or internal symbols to ensure maintainability without breaking external consumers.

The dead code removal process uses a deterministic preview workflow, generating automated removal previews for review. You apply changes only after verifying the preview and confirming the compile checks pass.

Automated dead code removal is limited to unreferenced private and internal symbols, conservatively preserving public APIs unless explicitly overridden. It requires reference verification and compile checks before applying any changes to prevent regressions.