careful

Detect destructive commands and prompt for confirmation before execution.

5|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill careful-drt0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-careful
Command: npx skills add https://github.com/drt0927/tw-overlay --skill careful-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides safety guardrails for destructive commands by warning before execution and allowing users to override warnings when appropriate, reducing the risk of accidental data loss.

Core Features & Use Cases

  • Real-time detection of dangerous operations across shells and tooling (e.g., rm -rf, git reset --hard, kubectl delete, DROP TABLE).
  • Interactive warnings with a user-driven override flow and audit logging to track potentially destructive actions.
  • Easy integration via a pre-execution hook that can be extended to additional tools in the future.

Quick Start

Enable careful mode to automatically warn before executing potentially destructive commands.

Frequently Asked Questions about careful

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

FAQPage Schema
Does this destructive command detection work across different shell and tooling environments?

Yes, real-time detection of dangerous operations works across shells and tooling environments including Git, Kubernetes, and database contexts, using a pre-execution hook that can be extended to additional tools in the future.

How do I add safety prompts for Kubernetes and database operations like kubectl delete and DROP TABLE?

Interactive safety prompts apply to Kubernetes and database contexts, detecting dangerous operations like kubectl delete and DROP TABLE to warn you before execution and allow a user-driven override flow.

What is the best way to guard destructive shell commands without blocking intentional force-pushes?

The best way to guard destructive shell commands is implementing a pre-execution hook that detects dangerous operations and issues interactive warnings, allowing you to override the alert when an intentional force-push is required.

How do I track when potentially destructive actions are executed in the terminal?

You can track potentially destructive actions by enabling a safety guardrail that provides audit logging, recording usage analytics every time a destructive command pattern triggers a warning or is executed.