safe-remove-code

Safe code removal uses mandatory backups, per-file validation, and syntax checks to prevent accidental damage. Create a timestamped backup first, apply precise patterns to target files, then validate each file individually and run functional tests to confirm the system still works.

Per-file validation checks syntax integrity, file size changes, and functional correctness after removal. This prevents gutting files by detecting when too much code was deleted or syntax became invalid, triggering rollback if any file fails validation.

Yes. The Skill removes instrumentation, debugging statements, and deprecated patterns from shell and script files using precise pattern matching, per-file validation, and syntax checks via bash -n or equivalent, ensuring hooks and critical scripts remain functional.

Test patterns locally against a small file set first to verify they match only intended code. Use exact, tested patterns rather than aggressive regex to avoid unintended deletions, then run the removal script with a test-command flag to validate syntax before committing changes.

Timestamped backups enable safe rollback if validation fails or removal goes wrong. Per-file validation detects damage immediately, allowing you to restore from backup and adjust patterns without data loss or manual restoration.

Yes. Functional testing after all removals verifies overall system integrity across your entire codebase. This catches edge cases where individual file validation passed but removal broke interdependent components or workflows.