---

name: safe-file-removal description: Use safe-rm command to safely 'remove' files by renaming them to .obsolete instead of permanent deletion. Reversible, collision-safe, hook-compliant. allowed-tools: Bash, Read, Grep

Safe File Removal

Rename files to .obsolete instead of permanent deletion via safe-rm command.

When to Use

• Removing temp files, build artifacts, old code, deprecated tests
• After refactoring (keep backup during testing)
• Any situation where rm is blocked by pre-tool hooks
• Need reversible "deletion"

Why Not rm

Project setting: .claude/settings.json:132 → "RM_BASH_BLOCK": "true"

Command

Copy./.claude/bin/safe-rm [file1] [file2] [dir/]

Path: .claude/bin/safe-rm:1-72

Features

Basic Usage

Recovery

Workflow

1. Mark obsolete → safe-rm [files]
2. Verify works → npm test && npm run build
3. Review periodic → find . -name "*.obsolete"
4. Permanent delete (when confident) → /bin/rm [file].obsolete

When NOT to Use

Output Examples

Success:

Copy✓ Renamed: file.txt → file.txt.obsolete
─────────────────────────────────────
Renamed: 1

Collision (timestamp fallback):

Copy⚠ Already exists: file.obsolete
  Using: file.obsolete.20251109_110500
✓ Renamed: file → file.obsolete.20251109_110500

Error:

Copy✗ Not found: missing.txt
─────────────────────────────────────
Failed: 1

Quick Reference

Supporting Files

• EXAMPLES.md - 10 scenarios: temp files, refactoring, tests, collisions, assets, docs, batch ops, scripting, git, hooks
• TEMPLATES.md - Copy-paste commands for all operations
• VALIDATION.md - Safety checklists, verification commands

Key Insight

Safety by design: No permanent deletion → collision protection → hook compliance → audit trail. Development workflow: Refactor → safe-rm → Test → Review period → Permanent delete after confidence.