careful

Detect and block destructive Bash commands like rm -rf and git push --force.

11|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill careful-pillip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/careful
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill careful-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental destructive actions by warning or blocking dangerous Bash commands in real-time during a session.

Core Features & Use Cases

  • Real-time detection of destructive patterns such as rm -rf, git push --force, git reset --hard, and other risky commands, with an explanatory block before execution.
  • Safe exemptions for common non-destructive commands and --dry-run usage to allow testing without applying changes.
  • Simple deactivation by starting a new conversation or avoiding the activation trigger.

Quick Start

Run /careful to activate destructive command warnings for your current session.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I prevent accidental execution of destructive Bash commands like rm -rf?

To prevent destructive Bash commands like rm -rf, you can activate a real-time warning system that blocks risky execution and prompts for confirmation. This protects your interactive sessions by detecting dangerous patterns before they run.

Can I test risky Bash commands without applying actual changes to my system?

Yes, you can test risky Bash commands without applying changes by using safe exemptions like the --dry-run flag. The detection mechanism allows these non-destructive operations to execute while blocking actual damaging actions.

How do I get a warning before running git push --force or git reset --hard?

You get a warning before running git push --force or git reset --hard by enabling a safety guard in your session. It identifies these specific risky patterns, blocks their execution, and provides clear guidance to re-run with confirmation.

How do I stop destructive command warnings from running in my terminal session?

To stop destructive command warnings from running in your terminal session, simply start a new conversation or avoid the activation trigger. The safety guard is scoped to your current session and does not permanently alter your environment.

Does the destructive command blocker work in automated scripts as well as interactive sessions?

Yes, the destructive command blocker works in both automated scripts and interactive sessions. It targets dangerous Bash operations across different execution contexts, blocking risky commands and prompting for confirmation before proceeding.