careful

Intercepts destructive shell commands before execution to prevent system damage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill intercepts destructive commands before execution, preventing accidental system damage in development and production contexts.

Core Features & Use Cases

  • Real-time detection of dangerous commands and prompt-based safety checks.
  • User override capability to proceed or cancel after a warning, enabling controlled experimentation in shared environments.
  • Local analytics logging to help audit usage and improve safeguards.

Quick Start

Enable careful mode and try a destructive command to see the warning.

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 push --force?

To prevent accidental execution of destructive shell commands, you need a pre-run hook that intercepts patterns like rm -rf or git push --force and triggers a real-time warning. This safety guardrail prompts you to proceed or cancel before any system damage occurs.

What is a pre-run hook for intercepting dangerous bash commands?

A pre-run hook for intercepting dangerous bash commands analyzes your input before execution, searching for risky patterns like git reset --hard or kubectl delete. It halts the operation and presents a prompt-based safety check to confirm your intent.

Can I override the safety warning if I need to force execute a command during debugging?

Yes, you can override the safety warning if you need to force execute a command during debugging. The user override capability allows you to bypass the prompt and proceed with the destructive action, enabling controlled experimentation in your environment.

Does this command interception work for shared production environments?

Yes, this command interception works for shared production environments. It applies across local and shared systems, guarding against risky actions during prod work and collaborations to prevent accidental system damage across your infrastructure.

How do I audit the usage of overridden destructive commands in my local environment?

To audit the usage of overridden destructive commands in your local environment, you can rely on local analytics logging. This feature records your interactions with the safety guardrails, helping you track when warnings were bypassed to improve future safeguards.