careful

You can add warning prompts to bash workflows to prevent risky git reset --hard execution. This skill intercepts high-risk commands before they run, requiring your explicit acknowledgment to proceed and preventing accidental repository state loss.

Yes, establishing safe exceptions for known build artifacts is necessary when adding destructive command guardrails. This skill automatically excludes known build artifacts from its risk pattern checks, ensuring routine build cleanups proceed without unnecessary warnings.

Yes, you can override the warning to proceed with a kubectl delete command. This skill features user-overrides that allow you to bypass the safety prompt and execute the high-risk operation after providing explicit acknowledgment of the potential impact.

A PreToolUse hook detects destructive shell commands by inspecting the command string for risk patterns before execution. This applies across staging and production environments, catching high-risk operations like DROP TABLE or kubectl delete before they run.