rule-code-preservation

To prevent silent code deletions during refactoring, enforce non-destructive edits by requiring explicit approvals before altering existing logic. This approach preserves backward compatibility and documents all change decisions directly in commits.

The best way to maintain backward compatibility across branches is to apply guardrails that preserve existing logic during maintenance tasks. This ensures intentional behavior remains intact and prevents accidental reversions in your codebase.

To ensure non-destructive changes in code reviews, inspect refactoring tasks to confirm all intentional code paths are preserved before committing. Explicitly document decisions in commits to maintain transparency and prevent silent reversions.

You need to enforce non-destructive code changes during refactors, maintenance tasks, and code reviews where backward compatibility matters. This prevents silent deletions and ensures existing behavior is explicitly preserved across sessions.

Yes, this approach requires explicit approval before removing or altering existing code. By enforcing non-destructive edits, it ensures that intentional code paths and backward compatibility are preserved during refactoring.

Refactoring causes silent reversions when changes are made without enforcing non-destructive edits or documenting decisions. Requiring explicit approvals before altering existing logic prevents these accidental deletions and maintains intentional behavior.