Safe Code Removal FAQs

Question 1

Can I use this for complex code refactoring?

Accepted Answer

No, this skill is specifically optimized for pattern-based removal (instrumentation, logs, etc.). For complex structural changes or refactoring, the standard Edit tool is more appropriate.

Question 2

Does it support languages other than Shell/Bash?

Accepted Answer

While the core logic uses Bash for execution, the principles of backup, precise pattern matching, and integrity checking can be applied to any text-based source code files.

Question 3

What happens if the code removal breaks my syntax?

Accepted Answer

The skill includes an automatic syntax check during the removal process. If a file fails validation, the script can automatically restore it from a mandatory backup created before the operation started.

Question 4

Why shouldn't I just use a global find-and-replace?

Accepted Answer

Global find-and-replace lacks context and per-file validation. This skill prevents 'gutting' files where a pattern might match more than intended by checking the remaining functional lines and syntax integrity.

Question 5

How do I ensure my backups are safe?

Accepted Answer

The skill creates timestamped backups before any changes are made and includes a verification step that ensures the number of backups matches the number of target files before proceeding.

Safe Code Removal

Características Principales

Casos de Uso

Safe Code Removal

Características Principales

Casos de Uso