careful

Intercept risky shell commands and prompt for confirmation before execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3.

What problem does it solve?

Safety guards run in the background to warn before executing destructive commands like rm -rf, DROP TABLE, git reset --hard, kubectl delete, or similar operations, preventing accidental data loss or system damage.

Core Features & Use Cases

  • Pre-command warnings for dangerous operations with optional overrides.
  • Safe exceptions for routine maintenance to avoid false positives.
  • Use cases include protecting production deployments, debugging live systems, and safeguarding shared environments.

Quick Start

Enable careful mode to warn before destructive commands and require confirmation.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I prevent accidental data loss from destructive shell commands like rm -rf or git reset --hard?

You can prevent accidental data loss from destructive shell commands by intercepting risky operations before they execute. This safety mechanism detects patterns like rm -rf and git reset --hard, prompting for confirmation before proceeding.

Can I add safe exceptions for routine kubectl delete commands to avoid false positives?

Yes, you can configure safe exceptions for routine maintenance to avoid false positives. This allows specific kubectl delete or related actions to execute without triggering the warning prompt.

Does this command warning system require python3 to run?

Yes, this command warning system requires python3 as a dependency to function. It uses python3 to implement the PreToolUse hook that intercepts and evaluates risky shell commands.

What is the best way to add guardrails for destructive commands across staging and production environments?

The best way to add guardrails for destructive commands across staging and production is to implement a PreToolUse hook. It detects risky actions and prompts for confirmation, safeguarding shared environments and deployments.

How does a PreToolUse hook intercept risky bash and devops commands?

A PreToolUse hook intercepts risky bash and devops commands by pattern matching the input against known destructive operations. When a match is found, it pauses execution and prompts the user for confirmation or override.

Will this destructive command guard block my live system debugging workflows?

No, this destructive command guard will not block live system debugging workflows because it prompts for confirmation rather than hard-stopping execution. You can override the warning or use safe exceptions for routine maintenance.