careful

Scan shell and Git commands for destructive patterns before execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents accidental destructive commands in your shell or Git commands by prompting before dangerous actions like deleting files, dropping tables, or force pushing in Git.

Core Features & Use Cases

  • Prevent Destructive Commands: Before executing commands like 'rm -rf', 'DROP TABLE', 'git reset --hard', etc., this Skill alerts you to potential dangers.
  • Selective Warnings: Allow specific patterns, such as cleaning build artifacts, without unnecessary prompts.
  • Safe to Deactivate: Skill can be easily deactivated if needed.

Quick Start

Before running 'rm -rf' or any similar command, use 'gstack careful be careful' to ensure safe operations.

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 Git commands like force push and reset hard?

To prevent destructive Git commands, this Skill scans your input against patterns like force push and git reset hard, prompting you to verify dangerous actions before execution in shared environments.

Can I get a warning before running destructive shell commands like rm -rf?

Yes, you can get a warning before running destructive shell commands by using this Skill to scan inputs like rm -rf and alert you to potential dangers before execution.

Does this destructive command detection tool allow specific safe patterns?

Yes, destructive command detection allows specific safe patterns, enabling you to permit operations like cleaning build artifacts without triggering unnecessary verification prompts.

How does selective warning work for shell and Git security?

Selective warning for shell and Git security works by verifying user input against dangerous manipulation patterns, prompting only for actions indicative of deletion or reset while allowing safe patterns.

When should I use a destructive command prevention tool in my workflow?

You should use destructive command prevention in shared or production environments where data integrity is paramount, ensuring safe operation by verifying dangerous system manipulation before execution.

Can I deactivate the bash security prompt if I need to force an operation?

Yes, you can deactivate the bash security prompt if needed, allowing you to bypass the destructive command detection and execute system manipulation actions without verification.