guard

Warn before destructive commands and restrict file edits to a selected directory.

2|1|Updated May 20, 2026

Search Tags:#development workflow #access control #safety #guardrails #file editing #command protection

Ready to run

npx skills add https://github.com/balajivis/multiagent-primer --skill guard-balajivis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/balajivis/multiagent-primer/tree/main/lab0-workflow/gstack/guard
Command: npx skills add https://github.com/balajivis/multiagent-primer --skill guard-balajivis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky changes during sensitive development work by combining destructive command warnings with strict directory-scoped edit protection.

Core Features & Use Cases

Destructive Command Protection: Warns users before potentially dangerous operations such as recursive deletion, database drops, or force pushes.
Directory Edit Boundaries: Restricts file modifications to a user-selected directory to reduce accidental changes outside the intended scope.
Use Case: Safeguard production debugging sessions by allowing necessary work inside a chosen folder while blocking unsafe commands and out-of-scope edits.

Quick Start

Use the guard skill to enable maximum safety mode and restrict all edits to the directory I specify.

Frequently Asked Questions about guard

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

FAQPage Schema

How do I prevent accidental file edits outside a specific directory during production debugging?▼

Preventing accidental file edits outside a specific directory during production debugging requires directory-scoped edit boundaries. This restricts file modifications to your selected folder, blocking out-of-scope changes while allowing necessary work inside.

What are safety guardrails for destructive commands in a development workflow?▼

Safety guardrails for destructive commands in a development workflow are protective hooks that warn users before executing potentially dangerous operations. They intercept risky actions like recursive deletion, database drops, or force pushes to prevent accidental damage.

How do I set up command protection and edit validation for high-risk repository changes?▼

Setting up command protection and edit validation for high-risk repository changes involves enabling safety hooks that enforce destructive command warnings alongside directory-scoped edit restrictions. This creates controlled modification boundaries for sensitive maintenance tasks.

Can I restrict file modifications to a selected folder for live system maintenance?▼

Yes, you can restrict file modifications to a selected folder for live system maintenance by applying directory edit boundaries. This enforces strict validation that actively reduces accidental changes outside your intended modification scope.

When do I need access control and safety hooks for development workflows?▼

You need access control and safety hooks for development workflows during sensitive operations like production debugging, live system maintenance, or high-risk repository changes. They provide controlled modification boundaries to prevent unauthorized edits and destructive commands.