careful

Monitor Bash script execution for destructive commands and request confirmation.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/26mitch26/ai-mall --skill careful-26mitch26
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/26mitch26/ai-mall/tree/main/.claude/skills/careful
Command: npx skills add https://github.com/26mitch26/ai-mall --skill careful-26mitch26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents accidental execution of dangerous commands, ensuring safety in scripts and system operations.

Core Features & Use Cases

  • Pre-Command Checks: Warns before running destructive commands like rm -rf, DROP TABLE, and git reset --hard.
  • Custom Triggers: Trigger warnings with keywords like "be careful", "warn before destructive", or "safety mode".
  • Integration: Works with tools like Bash and supports hooks for additional safety measures.

Quick Start

To enable safety checks, simply prepend your command with "be careful" or set the safety mode explicitly.

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 a script?

You can prevent destructive bash commands by enabling safety checks that monitor script execution for risky patterns and prompt user confirmation before proceeding. This intercepts dangerous operations to prevent accidental data loss during development.

How do I prompt for confirmation before running git reset hard or rm rf?

To prompt for confirmation before running git reset hard or rm rf, prepend your command with safety triggers like "be careful". This activates pre-command checks that warn before executing destructive operations.

Can I configure custom warning triggers for destructive command prevention in bash?

Yes, you can configure custom warning triggers for destructive command prevention in bash. This skill supports triggering warnings with custom keywords like "be careful", "warn before destructive", or "safety mode".

Does this command safety tool work in both development and production environments?

Yes, this command safety tool works in both development and production environments. It is specifically designed to maintain script safety and prevent system damage across different operational stages using bash hooks.

What are the limitations of using keyword triggers for script protection?

The limitation of using keyword triggers for script protection is that it requires explicit bash script execution and hook configuration. You must prepend commands with specific keywords or set safety mode to activate the destructive command checks.