skills.rest
studyzy
studyzyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

guard

Enforce destructive-command warnings and directory-based edit boundaries on production systems.

Updated Mar 21, 2026
Search Tags:#production#safety#guard#risk-reduction#destructive-warnings#edit-boundary
One-click install
npx skills add https://github.com/studyzy/dev-agent-protocol --skill guard-studyzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/studyzy/dev-agent-protocol/tree/main/.claude/skills/gstack/guard
Command: npx skills add https://github.com/studyzy/dev-agent-protocol --skill guard-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protects production and live systems by enforcing destructive-command warnings and a configurable edit boundary.

Core Features & Use Cases

  • Destructive-command warnings for risky operations such as rm -rf, DROP TABLE, and force-push scenarios.
  • Directory-boundary enforcement to restrict edits to a specific path, reducing accidental changes to critical files.
  • Use cases include debugging prod systems or making risky changes with guardrails, and quickly reversing protections when needed.

Quick Start

Ask the user which directory to restrict edits to, then enable both destructive-command warnings and the edit boundary protections.

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 in production?▼

Preventing accidental destructive commands in production involves enforcing warnings that intercept risky operations like rm -rf or DROP TABLE before they execute, ensuring actions stay within a safe scope.

How do I restrict file edits to a specific directory boundary?▼

Restricting file edits to a specific directory boundary requires configuring a persistent path enforcement rule that blocks any accidental modifications to critical files outside that designated scope.

What are destructive-command warnings and how do they work?▼

Destructive-command warnings are pre-check hooks that identify and halt high-risk terminal commands, such as force-push scenarios or database deletions, providing a guardrail during sensitive live system operations.

Can I quickly reverse edit boundary protections when debugging prod systems?▼

You can quickly reverse edit boundary protections when debugging prod systems by disabling the configured directory restrictions, allowing you to restore full access after your risky changes or deployment tasks are complete.

Do I need external scripts to enforce directory edit boundaries?▼

Enforcing directory edit boundaries relies on pre-check hooks and external scripts from sibling skills to validate the configured directory stored in persistent state, ensuring actions remain within the safe scope.

Related Skills

Explore More Software Engineering Skills→
geoffreywoogeoffreywoo

guard

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

Community
Advanced
fray-cloudfray-cloud

guard

Enforce destructive-command warnings and directory-scoped edit protections via PreToolUse hooks.

Community
Advanced
SeaLion-hubSeaLion-hub

guard

Warn before destructive commands and restrict file edits to approved directories.

Community
Advanced
KrismithReddy12KrismithReddy12

unfreeze

Remove directory-level edit restrictions by deleting the freeze state file.

Community
Basic