careful

Warn before executing destructive shell commands like rm -rf and kubectl delete.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/vib795/copilot-anatomy --skill careful-vib795
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: careful
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/gstack-careful
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill careful-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safety guardrails prevent accidental destructive actions by warning before commands like rm -rf, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning, enabling controlled risk in shared environments.

Core Features & Use Cases

  • Real-time destructive command detection: Intercepts dangerous commands and prompts for confirmation before execution.
  • Scope-aware safeguards: Applies in production, staging, and development environments with per-command risk patterns.
  • Audit and governance: Logs usage for auditing and post-incident review.

Quick Start

Run careful mode in your interactive shell to enable real-time warnings for destructive commands.

Frequently Asked Questions about careful

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

FAQPage Schema
How do I add safety warnings for destructive bash commands like rm -rf?▼

You can guard destructive bash commands by enabling a shell mode that intercepts risky operations and prompts for confirmation before execution. This safety mechanism applies per-command risk patterns to prevent accidental data loss.

Can I override the warning when running git reset --hard in staging environments?▼

Yes, you can override the warning when running git reset --hard in staging environments. The safety guardrails prompt for confirmation but allow controlled risk overrides, logging the incident for post-incident auditing.

Does this destructive command guard work with kubectl delete operations?▼

Yes, this destructive command guard works with kubectl delete operations. It detects risky actions in real-time and applies scope-aware safeguards across development, staging, and production environments before execution.

What is the best way to prevent accidental destructive actions in shared environments?▼

The best way to prevent accidental destructive actions in shared environments is implementing real-time command detection with pre-run guards. This intercepts dangerous shell operations, enforces confirmation prompts, and logs incidents for governance.

Are destructive command warnings logged for post-incident review?▼

Yes, destructive command warnings are logged for auditing and post-incident review. The governance mechanism captures usage data when intercepting risky operations, ensuring accountability even when users exercise override capabilities.

Do I need to configure separate rules for production and development environments?▼

No, you do not need to configure separate rules manually. The scope-aware safeguards automatically apply per-command risk patterns across production, staging, and development environments within your interactive shell session.