careful

Warn before executing destructive commands in interactive sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps prevent accidental damage by warning before executing dangerous commands like rm -rf or git push -f, keeping your environment safer during interactive sessions.

Core Features & Use Cases

  • Warns before destructive commands that could delete files or alter history (e.g., rm -rf, git push -f, git reset --hard, git clean -f, docker system prune).
  • Respects safe exceptions for commonly allowed operations (e.g., rm -rf node_modules/, .next/, dist/, build/, pycache/, .cache/, tmp/).
  • Activation and deactivation across a session with explicit user prompts and a session-wide safety mode.
  • Provides an audit trail and quick deactivation commands like turn off careful mode.

Quick Start

Invoke /careful to enable the safety mode at the start of a session, then answer prompts to proceed only after explicit confirmation.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I get a warning before running destructive shell commands like rm -rf?

To get warnings before destructive shell commands like rm -rf, you enable a safety mode that pattern-matches risks and prompts for real-time confirmation. This prevents accidental file deletion during interactive sessions.

Can I prevent accidental git push -f or git reset --hard without blocking safe operations?

Yes, you can prevent accidental git push -f or git reset --hard by using a safety mode that includes safe-exceptions for commonly allowed operations. This allows specific directories like node_modules to be deleted without triggering a warning.

What is the best way to enable a confirmation prompt for dangerous git and docker commands?

The best way to enable a confirmation prompt for dangerous git and docker commands is to activate a session-wide safety mode. This mode pattern-matches commands like docker system prune and requires explicit user approval before execution.

How do I turn off safety warnings for destructive commands when I no longer need them?

To turn off safety warnings for destructive commands, you can use quick deactivation commands to disable the safety mode. This immediately stops the real-time prompts and exits the session-wide confirmation requirement.

Does the destructive command warning system keep a log of what was approved?

Yes, the destructive command warning system maintains a per-session audit trail. This log records the commands you explicitly approved during the interactive session, providing a history of potentially dangerous operations.