cleanup-health-inline

Automated dead code cleanup requires a multi-phase workflow that detects, prioritizes, removes, and verifies code deletions. This process enforces a type-check and build gate between steps to ensure removals do not break existing functionality.

Safe dead code removal involves backing up files before edits, updating change logs, and enforcing a verification cycle. This orchestrated approach prioritizes detected code for deletion and generates reports to maintain software health.

Yes, inline dead code removal reads a generated dead-code report to identify targets. The workflow uses this static analysis input to coordinate detection, backup, removal, and verification phases across the codebase.

To prioritize and verify dead code deletions, the workflow orchestrates detection, applies priority-based cleanup, and runs type-check and build gates. It creates file backups before edits and generates summaries for verification.

An inline workflow reduces technical debt by enforcing a type-check and build gate between removal steps. It coordinates file backups and verification cycles to ensure code deletions maintain project stability.