dead-code-intolerance

To remove commented-out code blocks during a review, apply a strict deletion policy that flags non-executing code for elimination. This approach ensures only active, necessary code remains, improving overall readability and maintainability.

Dead code includes unused imports, unreachable branches, and commented-out blocks that clutter the codebase. It hinders developer productivity by confusing readers and should be eliminated to maintain a clean, maintainable codebase.

Clean up unused imports and stale TODO comments by enforcing strict deletion policies for non-executing code elements. Leveraging version control history allows safe removal, ensuring the repository remains lean and focused.

Yes, dead code elimination applies to all programming languages within the repository. It targets obsolete feature flags, unreachable branches, and unused imports universally to promote a clean codebase.

You should delete obsolete feature flags because leaving them creates technical debt and clutters the codebase. Strict removal of these non-executing elements reduces time spent deciphering obsolete code and improves developer efficiency.

The best way to eliminate unreachable branches while preserving context is leveraging version control history. This ensures deleted code can be retrieved if needed, allowing strict deletion policies to maintain a clean codebase safely.