careful

Intercept destructive bash commands before execution to prevent data loss.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accidentally running destructive commands like recursive file deletions, SQL DROP statements, force git pushes, or Kubernetes resource deletions can cause irreversible data loss, service outages, and hours of recovery work, especially when operating in production environments or shared team workspaces.

Core Features & Use Cases

  • Destructive Pattern Detection: Automatically flags high-risk bash commands including rm -rf, DROP TABLE/DROP DATABASE, TRUNCATE, git push --force, git reset --hard, kubectl delete, and docker system prune before they execute.
  • Safe Exception Handling: Allows unblocked execution of common non-destructive operations like deleting build artifacts (node_modules, dist, pycache) to avoid unnecessary workflow friction.
  • Use Case: A developer working on a live production server can run all commands with this guard active to prevent accidentally deleting critical system files or overwriting remote git history that would impact other team members.

Quick Start

Activate the careful skill before running any bash commands to automatically receive warnings for destructive operations and confirm or cancel each risky action to avoid accidental data loss.

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 bash commands like rm -rf or git push --force?

To prevent accidental data loss from destructive bash commands, you can use a command guard that intercepts risky operations like rm -rf, git push --force, and SQL DROP statements before execution. This allows you to confirm or cancel each action.

Does command safety protection block safe deletions like removing node_modules or build artifacts?

Command safety protection includes safe exception handling, allowing unblocked execution of common non-destructive operations like deleting build artifacts such as node_modules, dist, and __pycache__ to avoid unnecessary workflow friction.

Can I use a destructive command guard for Kubernetes orchestration and database management?

Yes, a destructive command guard applies to Kubernetes orchestration and database management by detecting high-risk patterns like kubectl delete commands, SQL DROP/TRUNCATE statements, and Docker prune operations before they execute in your environment.

How do I protect a live production server from accidental file deletions and remote git history overwrites?

To protect a live production server from accidental file deletions and remote git history overwrites, activate a command guard to automatically receive warnings for destructive operations and confirm each risky action before it impacts team members.

What is the best way to intercept risky DevOps commands before they execute in production environments?

The best way to intercept risky DevOps commands before execution in production environments is applying a bash guardrail that detects destructive patterns like recursive file deletion, hard git resets, and docker system prune, prompting for confirmation.