guard

Name: guard
Availability: InStock
Author: kunalrawat425

Warn on destructive commands and block edits outside a configured directory.

Updated Apr 4, 2026

Search Tags:#devops #safety #risk-management #freeze #boundary #guard #destructive-warnings

Ready to run

npx skills add https://github.com/kunalrawat425/conductor-playground --skill guard-kunalrawat425

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/kunalrawat425/conductor-playground/tree/main/.claude/skills/gstack/guard
Command: npx skills add https://github.com/kunalrawat425/conductor-playground --skill guard-kunalrawat425

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides dual safety mechanisms by issuing warnings for destructive commands and by enforcing a directory-based edit boundary to prevent risky changes in production or live systems.

Core Features & Use Cases

Destructive command warnings for rm -rf, DROP TABLE, force-push, and other high-risk operations.
Directory-bound edit restrictions via a configured freeze boundary to block edits outside a chosen path.
Unified safety mode when you want maximum protection during incident response, debugging, or prod maintenance.

Quick Start

Ask the user which directory should edits be restricted to and activate guard mode with that path.

Frequently Asked Questions about guard

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

FAQPage Schema

How do I prevent accidental destructive commands like rm -rf and DROP TABLE during production debugging?▼

To prevent destructive commands during production debugging, you need a safety mechanism that issues warnings for high-risk operations like rm -rf, DROP TABLE, and force-push. This approach establishes dual safety by enforcing directory-bound edit restrictions to block risky changes in live systems.

Can I restrict edits to a specific directory boundary during refactoring or auditing?▼

Yes, you can restrict edits to a specific directory boundary during refactoring or auditing by configuring a freeze boundary. This safety mode stores the boundary path in a state file to enforce editing restrictions and block any modifications outside that chosen directory.

How does a directory boundary edit restriction work for ops workflows?▼

A directory boundary edit restriction works for ops workflows by using pre-tool hooks to run readiness checks before allowing modifications. It relies on configured freeze boundaries to block edits outside a defined path, ensuring maximum protection during incident response and prod maintenance.

Do I need any additional components to enable maximum safety mode for critical edits?▼

Yes, to enable maximum safety mode for critical edits, you must install the sibling careful and freeze components. These required dependencies work alongside pre-tool hooks to execute readiness checks and properly enforce the directory-based edit restrictions.

What is the best way to protect critical systems from risky changes during incident response?▼

The best way to protect critical systems from risky changes during incident response is to activate a unified safety mode that combines destructive command warnings with directory-bound edit restrictions. This dual mechanism prevents high-risk operations and limits edits to an explicitly configured path.