careful

Scan Bash commands for destructive patterns before execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides safety guardrails for destructive commands by warning before potentially destructive actions such as rm -rf, DROP TABLE, git reset --hard, kubectl delete, and similar operations. Users can override warnings to proceed when necessary, enabling safe debugging in production-like environments.

Core Features & Use Cases

  • Destructive command detection for common risky operations (rm -rf, DROP TABLE, TRUNCATE, git push --force, git reset --hard, kubectl delete, docker system prune) with an option to override warnings.
  • Safe exceptions for common build artifacts (e.g., node_modules, .next, dist, pycache) to allow workflows without noise.
  • Hook-driven activation via PreToolUse to enforce safety before command execution.

Quick Start

Attempt a command in your shell; the guard will scan it for destructive patterns and prompt you to confirm or cancel.

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 bash commands like rm -rf from executing?

To prevent destructive commands like rm -rf from executing, you need a pre-tool check hook that scans input for risky patterns before execution and returns a permission decision to allow or prompt the user.

Can I override safety warnings for git reset --hard when I need to proceed?

Yes, you can override safety warnings for commands like git reset --hard; the guardrail intercepts the command and prompts you to confirm or cancel, enabling safe debugging in production-like environments.

Does the destructive command guard work with kubectl delete and docker system prune?

The destructive command guard works with kubectl delete, docker system prune, git push --force, DROP TABLE, TRUNCATE, and similar operations by scanning for risky patterns before execution in Bash environments.

Will build artifact directories like node_modules trigger destructive command warnings?

No, build artifact directories like node_modules, .next, dist, and __pycache__ have safe exceptions that allow workflows to proceed without noise, preventing unnecessary warning prompts during development.

What is the best way to add guardrails for risky shell operations without blocking all commands?

The best way to add guardrails for risky shell operations is hook-driven activation via PreToolUse, which enforces safety before command execution and returns a permission decision to either allow or prompt the user.

When do I need a pre-tool check hook for bash command safety?

You need a pre-tool check hook for bash command safety when working in production-like environments where destructive operations such as rm -rf, git reset --hard, or kubectl delete pose risks to your data.