scratch-trash-guard

Prevent accidental file deletion by enforcing a mandatory mode choice and a typed confirmation code before executing any destructive file operations. This two-step safety workflow ensures explicit user consent for requests to delete, remove, or purge files across projects.

Yes, you can move files to a dated trash directory instead of permanently deleting them. This safety mode preserves the original relative paths within the trash location, allowing you to safely archive or discard files while keeping a recoverable backup.

The confirmation code mechanism requires you to select a deletion mode and then type a generated, exact confirmation code before execution. This explicit consent step prevents unintended destructive actions by verifying clear user intent before proceeding.

The deletion confirmation workflow guards requests to delete, remove, clean up, purge, discard, or archive files and directories across projects. It intercepts these destructive file operations to enforce a mandatory mode choice and explicit user confirmation.

No external dependencies are required to use the file deletion safety guard. It operates independently to enforce explicit consent for destructive actions, generating unique confirmation codes and handling trash routing without additional modules.