careful

Scans commands for destructive patterns and prompts for permission before execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Destructive commands can cause data loss or system outages in shared or production environments. This skill provides proactive warnings and user-controlled overrides to prevent accidental damage.

Core Features & Use Cases

  • Warns before destructive operations such as rm -rf, DROP TABLE, git reset --hard, kubectl delete, and docker rm -f.
  • Lets users override warnings when necessary, enabling careful debugging or maintenance on live systems.
  • Suitable for development, staging, or production environments where safety and auditability are required.

Quick Start

Use the careful skill to enable a warning before a potentially destructive command in your shell session.

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 shell commands like rm -rf or git reset --hard?

You can prevent accidental destructive shell commands by using a pre-tool hook that scans for patterns like rm -rf or git reset --hard and prompts for permission before execution. This guard intercepts dangerous commands across development, staging, and production workflows.

Can I override the warning when I intentionally need to run a destructive command?

Yes, the safety guard provides overridable warnings, enabling you to bypass the prompt and execute destructive commands like kubectl delete or docker rm -f when necessary for careful debugging or live system maintenance.

Does this pre-hook guard work with database operations like DROP TABLE?

Yes, the pre-hook scans for destructive patterns including database commands like DROP TABLE. It warns before executing these irreversible operations, ensuring data loss prevention across shared and production environments.

What is the best way to add safety guardrails to destructive devops commands across staging and production?

The best way to add safety guardrails is implementing a pre-tool hook that scans for destructive devops commands such as kubectl delete and docker rm -f, prompting for confirmation to prevent system outages and data loss.

Do I need any dependencies to enable a warning before destructive commands in my shell session?

No dependencies are required to enable warnings before destructive commands. The guard functions as a standalone pre-tool hook in your shell session, scanning for dangerous patterns and prompting for permission without external components.

When should I not use an overridable safety guard for destructive commands?

You should not rely solely on overridable guards when running fully automated, unattended pipelines where interactive prompts cannot be answered, as the warning mechanism requires user confirmation before executing destructive patterns.