safe-code-modifications

Unused code removal requires verifying that imports, functions, variables, and constants have no remaining references before deletion. This Skill provides comprehensive verification checks and language-specific guidelines to ensure safe code refactoring without introducing bugs.

Identifying unused imports and variables involves scanning the local source code repository to detect unreferenced functions and constants. This Skill automates this verification process using applicable language-specific tools to ensure safe code removal.

Yes, safe code removal provides language-specific guidelines and best practices for different programming languages. It checks for unused imports, functions, and variables correctly by applying rules tailored to each language's specific syntax and tooling.

Before deleting functions during legacy code refactoring, you must verify that the functions, variables, and constants are not in use anywhere in the local codebase. This ensures safe removal and maintains code safety without introducing regressions.

You should avoid automated code removal without verification when you lack local codebase access or applicable language-specific tools. Safe code removal requires thorough verification to prevent unintended deletions of seemingly unused imports or variables during maintenance.