careful

Warns before destructive commands execute and requires user confirmation via PreToolUse hook.

10|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/olaafrossi/FoamPilot --skill careful-olaafrossi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/careful
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill careful-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safety guardrails warn before destructive operations such as rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar actions, and allow user overrides when needed.

Core Features & Use Cases

  • Warn before executing dangerous commands in Bash environments.
  • Allow user override to proceed or cancel.
  • Applicable to development, staging, and production workflows to prevent accidental data loss.

Quick Start

Enable careful mode before executing any destructive command.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I add safety guardrails to warn before executing destructive bash commands?

Safety guardrails intercept destructive bash commands by triggering a warning prompt before execution. You enable careful mode in your interactive terminal or automated workflow to require user confirmation before proceeding.

Can I override the warning and proceed if a destructive command is blocked?

Yes, you can override the warning to proceed with the destructive command. The guardrail prompts for user confirmation, allowing you to explicitly choose to execute the blocked operation or cancel it entirely.

Does this protection work with commands like git reset --hard and kubectl delete?

Yes, this protection works with git reset --hard, kubectl delete, DROP TABLE, and rm -rf. It applies safety guardrails across development, staging, and production workflows to prevent accidental data loss.

How do safety guardrails protect automated workflows from accidental data loss?

Safety guardrails protect automated workflows by defining a PreToolUse hook that delegates to a bash script. This mechanism intercepts harmful commands and requires explicit confirmation before execution can proceed.

What's the best way to prevent accidental force-push or DROP TABLE operations in a terminal?

The best way to prevent accidental force-push or DROP TABLE operations is to enable careful mode. This marks the skill as sensitive and establishes session-scoped protection that warns before any destructive command runs.

What are the limitations of using a bash script for command interception?

Using a bash script for command interception requires a compatible Bash environment. The guardrail mechanism relies on a PreToolUse hook, meaning it only protects workflows where the hook can successfully delegate to the script.