safe-file-deletion

The safe-file-deletion Skill enforces explicit user permission before executing rm, rm -rf, unlink, or fs.rm commands. It intercepts the file deletion request, requires a JSON payload with file paths, and pauses to obtain user consent prior to execution.

Yes, you can batch delete multiple files by providing an array of file paths in the JSON payload. The Skill handles the batch deletion operation while ensuring explicit user consent is obtained before any files are removed.

The best way to prevent accidental data loss is to enforce mandatory confirmation before file removal. This Skill pauses script execution when a deletion is attempted on critical files, requiring explicit approval to prevent unauthorized or accidental deletion.

Yes, this file deletion safety mechanism works with programmatic operations like unlink and fs.rm. It intercepts these programmatic file system calls and requires explicit user permission before allowing the deletion to proceed.

You need to provide file paths in a JSON payload format specifying either a single file path or an array of file paths. This payload structure allows the Skill to identify the targets and request explicit user consent before deletion.