careful

Warn before destructive Bash commands like rm -rf and git reset --hard.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides safety guardrails to reduce the risk of destructive commands executing accidentally by warning users before potentially dangerous actions.

Core Features & Use Cases

  • Destructive command detection: warns before rm -rf, git reset --hard, kubectl delete, and similar actions.
  • Override capability: lets users proceed after a warning when they truly intend to perform the action.
  • Pre-execution hook integration: hooks are invoked by the PreToolUse phase to guard tools like Bash.

Quick Start

Enable careful mode before executing destructive commands to receive a warning and confirmation prompt.

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 in production?

This Skill prevents accidental destructive bash commands by implementing a PreToolUse hook that warns you before executing patterns like rm -rf or git reset --hard, requiring an explicit override to proceed.

Can I override the safety warning if I truly intend to run git reset --hard?

Yes, you can override the safety warning when you truly intend to run git reset --hard. The guardrail prompts for confirmation, allowing you to explicitly bypass the block and proceed with the destructive command.

What destructive command patterns does the PreToolUse hook detect?

The PreToolUse hook detects destructive command patterns including rm -rf, force-push, kubectl delete, and git reset --hard. It runs a safety script to intercept these actions during production debugging and shared environment workflows.

Does this guardrail work for kubectl delete operations in shared environments?

Yes, this guardrail works for kubectl delete operations in shared environments. It detects kubectl delete as a destructive pattern and warns you before execution, ensuring safe production debugging and shared environment management.

What is the best way to add guardrails for force-push and other destructive git actions?

The best way to add guardrails for destructive git actions like force-push is using a PreToolUse Bash hook. This mechanism automatically intercepts dangerous commands, requiring manual confirmation before any execution proceeds.