careful

To add safety prompts for destructive bash commands, this Skill uses a PreToolUse hook to inspect patterns like rm -rf before execution. It automatically intercepts the command and prompts you for confirmation, allowing you to override the warning if the action is intentional.

Yes, you can block git reset --hard and kubectl delete operations in shared production environments. The Skill detects these specific destructive commands via pattern matching and issues a warning prompt with an override option.

The best way to guard against accidental DROP TABLE statements in shell scripts is using a PreToolUse safety hook. It automatically detects dangerous database reset patterns and prompts you for explicit confirmation before allowing the script to proceed.

Safe exceptions for destructive command guardrails work by allowing common benign paths, such as temporary artifact cleanup, to execute without prompts. You can explicitly override warnings for blocked commands while the system maintains audit logging for controlled changes.

You should use a safety guardrail for destructive shell commands when touching production, debugging live systems, or working in a shared environment. It is specifically designed for scenarios requiring careful execution to prevent irreversible data loss.

Pattern matching for command safety prompts relies on detecting specific destructive patterns like force-push or deletions. While it provides an override path with audit logging, highly obfuscated commands or unrecognized destructive aliases might bypass the predefined pattern rules.