safety/mutation-approval

Requiring explicit user confirmation before destructive file mutations prevents unintended changes by intercepting operations, presenting a human-readable briefing, and logging approvals before execution proceeds.

Auditing destructive file operations for governance requires logging each mutation approval with a full audit trail, capturing pre-mutation briefings and rollback events to ensure traceability and safety compliance.

Partial approvals allow you to selectively accept individual mutations within a batch, preserving safety by ensuring only explicitly confirmed destructive operations proceed while others are held back.

Mutation approval applies to Claws with filesystem:write_user permission in both personal and project workspaces, intercepting destructive mutations regardless of workspace context to enforce confirmation gates.

Irreversible operation handling enforces dedicated safety gates that require heightened explicit confirmation before executing destructive mutations, preventing silent data loss and preserving auditability.

Destructive file mutations execute silently when mutation approval is not enabled, so enabling this Skill in your Claw workflow intercepts operations and enforces explicit confirmation before any changes commit.