careful

Prevent accidental data loss from destructive bash commands by implementing a PreToolUse hook that intercepts operations like rm -rf, warns before execution, and allows a user override. It protects interactive shells and automation pipelines by blocking or warning on matches.

Yes, you can get a warning prompt before running git reset --hard or kubectl delete in production by enabling careful mode. It interrogates dangerous commands in your development workflow, blocks them, and selectively allows you to override warnings after confirmation.

The best way to add safety guardrails to destructive commands in automation pipelines is to use a PreToolUse hook that interrogates bash commands, warns on destructive matches, and logs incidents. This approach prevents data loss across staging and production workflows.

Careful mode blocks force-push, DROP TABLE, and similar destructive operations by warning the user before execution. You can selectively override the warning to proceed with the command, while the system optionally logs the incident for review.

You need safety guardrails for destructive commands in a shared environment when touching prod, debugging live systems, or executing operations like git reset --hard. Implementing warning prompts prevents irreversible data loss across development, staging, and production workflows.