careful

Warn before destructive shell commands and require explicit override.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill careful-bradliebs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.gstack/careful
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill careful-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safety guardrails for destructive commands in Bash. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching production systems, debugging live environments, or working in a shared environment. (gstack)

Core Features & Use Cases

  • Real-time warnings before destructive commands across local shells and scripts.
  • Per-command override capability to proceed or cancel with an explicit confirmation.
  • Auditable logging of attempted dangerous commands for incident analysis.

Quick Start

Enable careful mode by loading the guardrails hook and run a destructive command to observe the warning.

Frequently Asked Questions about careful

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add safety guardrails to warn before destructive bash commands like rm -rf?

To add safety guardrails for destructive bash commands, load a PreToolUse Bash hook that intercepts commands like rm -rf or git reset --hard, warns you, and requires explicit override to proceed. This prevents accidental data loss.

What is a bash warning system for destructive shell commands?

A bash warning system for destructive shell commands is a PreToolUse hook that monitors operations like DROP TABLE and kubectl delete, issuing real-time warnings and requiring per-command override confirmation to prevent service disruption.

Can I override the warning when running dangerous commands in production environments?

Yes, you can override the warning when running dangerous commands in production environments. The guardrail system provides per-command override capability, allowing you to explicitly confirm and proceed or cancel the destructive operation.

Does the bash shell guardrails hook work for shared development environments?

Yes, the bash shell guardrails hook works for shared development environments. It provides real-time warnings before destructive operations and maintains auditable logging of attempted dangerous commands for incident analysis.

How do I log attempted dangerous shell commands for incident analysis?

To log attempted dangerous shell commands for incident analysis, use a bash guardrail system with auditable logging. It records intercepted dangerous operations like force-push or git reset --hard, providing a trail for post-incident review.