guard

Warn before destructive commands and restrict edits to a specified directory.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sadie100/claude-dotfiles --skill guard-sadie100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/sadie100/claude-dotfiles/tree/main/skills/guard
Command: npx skills add https://github.com/sadie100/claude-dotfiles --skill guard-sadie100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, and includes scripts (resource) components.

What problem does it solve?

This Skill enhances safety by providing warnings for destructive commands and restricting edits to a specified directory, mitigating risks in critical operations.

Core Features & Use Cases

  • Destructive Command Warnings: Alerts before executing commands like rm -rf, DROP TABLE, and force-push.
  • Directory-Scope Edits: Restricts file edits to a specified directory, preventing unintended modifications.
  • Use Case: When working on production systems or debugging live environments, this Skill can help prevent costly mistakes by ensuring that only authorized changes are made.

Quick Start

Set up guard mode for a specific directory and enable warnings for destructive commands.

Frequently Asked Questions about guard

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

FAQPage Schema
How do I prevent destructive commands like rm -rf from running in production systems?

To prevent destructive commands in production systems, this Skill provides warnings before executing commands like rm -rf, DROP TABLE, and force-push. It enforces directory-scoped edits to mitigate risks during critical operations.

Can I restrict file edits to a specific directory using bash scripts?

Yes, you can restrict file edits to a specific directory using bash scripts. This Skill enforces directory-scope edits, preventing unintended modifications to files outside the authorized target path during system operations.

What is the best way to add safety warnings for live environment debugging?

The best way to add safety warnings for live environment debugging is to enable command checking. This Skill alerts you before executing destructive commands, ensuring only authorized changes are made to critical environments.

Does this command checking tool require any specific dependencies?

Yes, this command checking tool requires bash as a dependency. It utilizes bash scripts to perform command checking and directory restriction for preventing unintended modifications in production systems.

How do I set up directory-scoped edits and command warnings?

To set up directory-scoped edits and command warnings, configure guard mode for a specific directory. This activates warnings for destructive commands and restricts file modifications to the specified path.