careful

Prompt before executing destructive shell, version control, and container commands.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/cattboy/lil_bro --skill careful-cattboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/cattboy/lil_bro/tree/main/.claude/skills/careful
Command: npx skills add https://github.com/cattboy/lil_bro --skill careful-cattboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental destructive operations by warning before executing dangerous commands.

Core Features & Use Cases

  • Proactive safety: warns before destructive actions like rm -rf, git reset --hard, kubectl delete, and other dangerous commands.
  • Configurable guardrails: allows user-specified overrides and safe-exceptions for common build artifacts.
  • Audit-friendly logging: records usage analytics for auditing and improvement.

Quick Start

Enable careful mode and confirm warnings before proceeding with 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 prevent accidental destructive commands like rm -rf or git reset --hard in bash?

To prevent accidental destructive commands, you can enable careful mode to intercept dangerous shell, version control, and container operations. It prompts for confirmation before executing actions like rm -rf or git reset --hard, adding proactive safety guardrails to your workflow.

Can I configure safety guardrails to allow specific overrides for build artifacts?

Yes, safety guardrails are fully configurable and support user-specified overrides. You can define safe-exceptions for common build artifacts, ensuring that prompt warnings do not interrupt necessary routine deletions while still protecting critical files.

Does this destructive command protection apply to container workflows like kubectl delete?

Yes, destructive command protection applies across shell, version control, and container workflows. It actively intercepts dangerous operations like kubectl delete, enforcing session-level prompts to minimize the risk of accidental infrastructure deletion.

How does logging work for audited destructive shell commands?

Logging for destructive shell commands records usage analytics whenever a prompt is triggered or bypassed. This audit-friendly logging captures the executed commands and override actions, providing an auditable trail for reviewing safety incidents and improving guardrail rules.

What is the best way to add prompt warnings for dangerous git commands?

The best way to add prompt warnings for dangerous git commands is to enable a careful mode session. This enforces configurable guardrails that automatically detect actions like git reset --hard, prompting you for confirmation before any irreversible version control changes are executed.