careful

Block destructive Bash commands before execution with user overrides.

15|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/howdeploy/NekoFree --skill careful-howdeploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/howdeploy/NekoFree/tree/main/skills/careful
Command: npx skills add https://github.com/howdeploy/NekoFree --skill careful-howdeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safety guardrails for destructive commands. 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 prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode". (gstack)

Core Features & Use Cases

  • PreToolUse hook for Bash: checks commands for destructive patterns before execution.
  • Safe exceptions for certain artifacts (e.g., rm -rf node_modules / build directories) to avoid over-warning during builds.
  • Logging of risk events to ~/.gstack/analytics/skill-usage.jsonl for auditability.
  • User override capability to proceed after warnings.

Quick Start

Enable careful mode and begin issuing Bash commands to receive warnings before any destructive operation.

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 block destructive bash commands?

Safety guardrails intercept destructive bash commands like rm -rf and DROP TABLE via precheck hooks, warning you before execution across development, staging, and production workflows. You can override each warning to proceed when appropriate.

Can I prevent accidental git reset --hard and force-push in production environments?

Yes, destructive operations including git reset --hard, force-push, and kubectl delete are identified and blocked before execution to protect production environments. The system applies precheck hooks to Bash operations and allows user overrides per warning.

How do I stop warnings for safe build artifacts like node_modules without disabling safety mode entirely?

Safe exceptions prevent over-warning during builds by allowing specific artifacts like rm -rf node_modules and build directories to execute without triggering destructive command warnings, keeping safety guardrails active for actual threats.

Does careful mode log destructive command attempts for auditability?

Yes, careful mode logs risk events to ~/.gstack/analytics/skill-usage.jsonl for auditability. This incident logging tracks destructive command warnings and overrides across development, staging, and production workflows.

What is the best way to activate safety prompts when debugging live systems?

Enable careful mode to activate safety prompts when debugging live systems or working in shared environments. The PreToolUse hook automatically checks Bash commands for destructive patterns and prompts you before any dangerous operation executes.