careful

Warn before destructive commands like rm -rf and DROP TABLE.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

  • Warning and optional override for dangerous commands
  • Culture-driven safety policies (deny/warn/allow)
  • Works across Bash workflows and collaborative environments

Quick Start

Ask me to enable careful mode before running any destructive command.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I add safety guardrails to prevent destructive bash commands in production?

To add safety guardrails for destructive bash commands, enable careful mode to intercept operations like rm -rf, git reset --hard, and kubectl delete. A pre-tool hook evaluates actions against culture risk gates, issuing warnings or blocking execution before touching production environments.

Can I override or bypass warnings for specific destructive shell commands?

Yes, you can override warnings for destructive shell commands when safety guardrails are active. The system prompts before executing operations like force-push or DROP TABLE, allowing you to explicitly bypass the block and proceed with the command if you accept the risk.

Does this safety mode work across collaborative environments and shared shell sessions?

Yes, careful mode works across bash workflows and collaborative environments. It enforces command overrides and safety checks during shared sessions, preventing users from accidentally executing destructive operations like DROP TABLE or kubectl delete on shared data.

What is the best way to warn developers before they run git reset --hard or force-push?

The best way to warn developers before running git reset --hard or force-push is to apply a pre-tool hook. This hook inspects commands, evaluates them against configured culture risk policies, and blocks or warns the user before execution proceeds.

How do I configure culture-driven safety policies to deny or allow specific bash commands?

To configure culture-driven safety policies, set the risk gates to deny, warn, or allow specific destructive bash commands. The pre-tool hook uses these defaults to determine whether to block operations like rm -rf or permit optional overrides.

When should I enable careful mode for my bash workflows?

Enable careful mode for bash workflows when touching production, debugging live systems, or working in shared environments. It provides necessary safety guardrails to prevent accidental data loss from destructive commands like kubectl delete or DROP TABLE.