careful

Analyze commands for destructive patterns and return permission decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In environments where destructive commands can cause major damage, this Skill provides automated guardrails that warn before proceeding and require explicit confirmation to execute dangerous actions.

Core Features & Use Cases

  • Destructive-command detection for bash and common tooling (rm, git, kubectl, etc.).
  • Optional override mechanism to proceed after a warning in controlled scenarios.
  • Seamless integration as a PreToolUse hook to audit commands before they are executed.

Quick Start

Enable careful mode and attempt a destructive command to see the warning prompt before execution.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I prevent destructive bash commands from running in a production environment?

You prevent destructive bash commands by applying a PreToolUse hook that scans user input for dangerous patterns and returns a permission decision to warn or allow before execution.

What is a PreToolUse hook for shell safety and how does it work?

A PreToolUse hook for shell safety analyzes commands before they are executed, scanning for destructive patterns to enforce guardrails and require explicit confirmation to proceed.

Can I override the warning and proceed with a flagged destructive command?

Yes, you can proceed after a warning using an optional override mechanism that allows controlled execution of destructive commands in scenarios where the action is intended.

Does this command filter support tools like git and kubectl, or just bash?

This command filter supports bash and common tooling including git and kubectl, detecting destructive commands across shared environments to prevent unintended system changes.

What's the best way to add guardrails for live-prod debugging sessions?

The best way to add guardrails for live-prod debugging is to enable automated command detection that warns before proceeding and requires explicit confirmation to execute destructive actions.