careful

Warn before executing destructive shell and deployment commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safety guardrails for destructive commands to prevent accidental data loss and system damage in shells, deployments, and shared environments.

Core Features & Use Cases

  • Warns before destructive commands such as rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar operations.
  • Allows user overrides to proceed after warnings.
  • Integrates as a PreToolUse hook that enforces safety in AI-assisted workflows.

Quick Start

Enable careful mode to prompt before destructive commands and review warnings before proceeding.

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 bash commands like rm -rf in production?

To prevent destructive bash commands in production, you need safety guardrails that intercept risky shell operations before execution. This skill implements a pre-tool use hook that analyzes shell commands for risky patterns like rm -rf and prompts for an explicit override before proceeding.

Can I get a warning before running kubectl delete or git reset --hard in shared environments?

Yes, you can get warnings before running kubectl delete or git reset --hard in shared environments. The guardrail mechanism analyzes cluster management and git operations for destructive patterns, presenting an explicit override option to proceed.

How does a PreToolUse hook work for blocking destructive database commands?

A PreToolUse hook for blocking destructive database commands works by analyzing commands like DROP TABLE before execution. It identifies risky patterns in database operations and forces an explicit user override to proceed, preventing data loss.

What is the best way to add safety guardrails to AI-assisted deployment workflows?

The best way to add safety guardrails to AI-assisted deployment workflows is integrating a PreToolUse hook. This enforces safety by analyzing shell and deployment commands for destructive patterns and requiring explicit overrides before execution in production.

Can I override the warning and still execute a force-push if I need to?

Yes, you can override the warning and still execute a force-push if needed. The guardrail presents an explicit override option after issuing the warning, allowing you to proceed with destructive commands intentionally when necessary.