careful

Warn before executing destructive commands in Bash and similar environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents accidental execution of destructive commands like 'rm -rf', 'DROP TABLE', and 'git reset --hard' by providing warnings before such actions.

Core Features & Use Cases

  • Prevent Destructive Commands: Alerts users before running potentially harmful commands.
  • Customizable Warnings: Users can configure which commands to warn about.
  • Use Case: Ideal for developers working in shared environments or on live systems to avoid data loss or system corruption.

Quick Start

Use the 'careful' skill to check your next destructive command and avoid any mistakes.

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 commands in Bash?

To prevent accidental execution of destructive commands in Bash, you can use command guardrails that monitor and provide warnings before running potentially harmful patterns. This helps avoid system damage and data loss.

Can I get warnings before running destructive Git commands like reset --hard?

Yes, you can get warnings before running destructive Git commands like reset --hard by checking command patterns against predefined destructive command lists. This alerts you before such actions execute.

Does command guardrail protection work with kubectl and shared development environments?

Command guardrail protection works with kubectl and similar environments to protect against accidental data loss in development and production workflows. It is ideal for developers working on shared live systems.

How do I customize warnings for specific destructive commands?

You can customize warnings for specific destructive commands by configuring which command patterns trigger alerts. This allows you to tailor the safety mode to your specific operational needs.

What is the best way to protect production systems from accidental data loss?

The best way to protect production systems from accidental data loss is implementing safety mode guardrails that check commands against predefined destructive lists. This prevents system corruption before execution.

What are the limitations of using predefined lists for command safety checks?

A limitation of using predefined lists for command safety checks is that they only protect against known destructive command patterns. Novel or obfuscated harmful commands might bypass these specific guardrails.