careful

Warn before destructive Bash commands execute via a PreToolUse hook.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent accidental destructive commands from executing in critical environments.

Core Features & Use Cases

  • Warns before destructive operations like rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar risky actions.
  • Allows user override for each warning after a prompt, enabling safe debugging and shared environment workflows.
  • Use when you need to prevent accidental data loss in prod or during collaborative development.

Quick Start

Activate careful mode in your Bash workflow to prompt before destructive commands.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I prevent accidental rm -rf or DROP TABLE commands from executing in Bash?

To prevent destructive commands in Bash, you can use a pre-execution hook that analyzes patterns like rm -rf or DROP TABLE and returns a permission decision with a warning before execution.

Can I override the warning when running destructive commands like git reset --hard?

Yes, you can override the warning for destructive commands like git reset --hard by providing explicit user permission after the prompt, allowing safe debugging and collaborative workflows to continue.

What is the best way to add safety guardrails for kubectl delete in shared environments?

The best way to add safety guardrails for kubectl delete in shared environments is using a Bash pre-execution hook that detects risky patterns and warns before the command executes.

Does this destructive command warning system work with force-push and database operations?

Yes, the destructive command warning system works with force-push and database operations by analyzing the command through a pre-execution hook and prompting for explicit override when a match is detected.

When do I need a pre-execution hook to warn on destructive commands?

You need a pre-execution hook to warn on destructive commands when you want to prevent accidental data loss in production or during collaborative development across local and shared environments.