avad-careful

Detect destructive Bash commands and require permission before execution.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/agwacom/avadbot --skill avad-careful
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avad-careful
Source: https://github.com/agwacom/avadbot/tree/main/skills/avad-careful
Command: npx skills add https://github.com/agwacom/avadbot --skill avad-careful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides safety guardrails for destructive commands, ensuring dangerous actions are detected and require explicit user confirmation before execution.

Core Features & Use Cases

  • Command monitoring: Intercepts and analyzes Bash commands for destructive patterns like rm -rf, git reset --hard, and kubectl delete.
  • Guarded execution: Prompts the user for permission, allowing explicit override when necessary.
  • Scope: Useful in development, staging, and production debugging environments to prevent data loss or service disruption.

Quick Start

To enable safe mode while running commands, prompt the system to validate the next destructive operation.

Frequently Asked Questions about avad-careful

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

FAQPage Schema
How do I prevent destructive bash commands like rm -rf from executing accidentally?

Safety guardrails intercept destructive bash commands like rm -rf before execution. The system analyzes command patterns and prompts the user for explicit permission, ensuring dangerous actions require confirmation to prevent accidental data loss.

Does this safety guardrail work with git reset --hard and kubectl delete commands?

Yes, the safety guardrail works with git reset --hard and kubectl delete commands. It monitors Bash-like environments to detect these destructive patterns and halts execution to prompt the user for explicit permission before proceeding.

Can I override the permission prompt for authorized destructive commands?

You can override the permission prompt for authorized destructive commands. The safety guardrail provides an explicit override option, allowing users to bypass the confirmation requirement when running necessary destructive tasks in development or staging environments.

What is the best way to add safety guardrails for destructive actions in production debugging?

Safety guardrails analyze destructive command patterns to provide protection during production debugging. By intercepting commands like rm -rf and git reset --hard, the system prevents service disruption and data loss by requiring explicit user confirmation before execution.

How do I set up pre-execution command monitoring for destructive bash patterns?

Pre-execution command monitoring is enabled by prompting the system to validate the next destructive operation. The skill analyzes Bash commands for destructive patterns and automatically halts execution to request user permission before any dangerous action proceeds.