careful

Warn before executing destructive Bash commands via a PreToolUse hook.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/legotec73/gstack --skill careful-legotec73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/legotec73/gstack/tree/main/careful
Command: npx skills add https://github.com/legotec73/gstack --skill careful-legotec73

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, grep, sed, python3.

What problem does it solve?

Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode".

Core Features & Use Cases

  • Pre-run analysis of dangerous commands and immediate warnings to prevent accidental data loss.
  • Flexible guardrails with per-command override options to maintain workflow while protecting critical assets.
  • Use cases include debugging live systems, making changes in shared environments, or performing maintenance on production-like systems.

Quick Start

Describe the destructive command you are about to run and let careful warn you with an option to proceed or cancel.

Frequently Asked Questions about careful

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent destructive bash commands like rm -rf from running accidentally?

Guarding destructive commands like rm -rf requires a PreToolUse hook that analyzes commands before execution. This Skill intercepts dangerous bash operations in interactive shells or scripts, returning a permission decision to ask or allow before proceeding.

Can I add safety guardrails for git reset --hard and kubectl delete in CI pipelines?

Yes, safety guardrails for git reset --hard and kubectl delete can be applied across CI pipelines and automated scripts. The mechanism analyzes commands and logs usage for auditing while providing per-command override options to maintain workflow.

Does this safety mode tool work with python3 and bash environments?

Yes, this safety mode tool works with python3 and bash environments. It depends on bash, grep, sed, and python3 to analyze commands and return permission decisions, applying effectively across shared environments and live system debugging.

What is the best way to warn before executing DROP TABLE statements in automated scripts?

The best way to warn before executing DROP TABLE statements in automated scripts is using a PreToolUse hook that analyzes commands for destructive operations. This approach returns a permission decision of ask or allow, enabling user overrides while logging usage for auditing.

How do I override a destructive command warning when debugging live systems?

Overriding a destructive command warning when debugging live systems is handled via per-command override options. When the guardrail intercepts an operation like force-push, it prompts the user, allowing you to proceed with the action or cancel it entirely.