careful

You can add safety warnings for destructive bash commands using a PreToolUse hook that pattern-matches commands like rm -rf or git push force and prompts for confirmation before execution.

Yes, safety guardrails can intercept destructive kubectl delete or docker commands in production environments, prompting you for confirmation or cancellation before the operation executes.

You can prevent false positives by defining safe exceptions for known targets, ensuring the pattern matching only halts genuinely destructive shell commands while allowing safe operations to proceed.

The best way to guard against accidental git reset hard in CI/CD pipelines is implementing a PreToolUse hook that detects destructive patterns and requires explicit user override to proceed.

Yes, the destructive command blocker works across multiple command-line tools including git, bash, kubectl, and docker, applying safety guardrails in development, CI/CD, and production contexts.

Yes, usage analytics are logged locally to ~/.gstack/analytics, providing an audit trail of when destructive command warnings are triggered and overridden for future review and improvement.