guard

Warn before destructive commands and block edits outside a protected directory.

Updated Aug 2, 2025
One-click install
npx skills add https://github.com/JovieInc/Jovie --skill guard-jovieinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/JovieInc/Jovie/tree/main/.claude/skills/gstack/guard
Command: npx skills add https://github.com/JovieInc/Jovie --skill guard-jovieinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental or destructive actions by enabling combined safety safeguards that warn before dangerous commands and block edits beyond a protected directory.

Core Features & Use Cases

  • Combines destructive command warnings with a directory-bound edit boundary to prevent risky changes during critical work.
  • Provides pre-use hooks that verify safety constraints before any tool execution, reducing human error in prod or sensitive environments.
  • Use Case: Operators debugging live systems can enable guard mode to ensure edits stay within a designated path and destructive actions are warned or blocked.

Quick Start

Ask the system to enable guard mode and specify the directory to protect.

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 during production maintenance?

Preventing accidental destructive commands during production maintenance requires enabling guard mode to activate pre-use hooks that verify safety constraints and warn before risky actions execute.

What is directory-bound edit boundary enforcement for development safety?

Directory-bound edit boundary enforcement blocks file modifications beyond a protected path, ensuring debugging and development edits stay contained within a designated directory to prevent outages.

How do I set up guard mode to protect a specific directory?

To set up guard mode, ask the system to enable it and specify the directory to protect, activating combined safeguards that warn on destructive commands and block out-of-bound edits.

Can I use boundary-aware automation for debugging live systems?

Boundary-aware automation is suited for debugging live systems, coordinating pre-use checks and edit boundaries to ensure operators make changes only within designated paths and avoid risky destructive actions.

What's the best way to implement pre-use safety checks for software engineering workflows?

Implementing pre-use safety checks for software engineering workflows is best achieved by combining destructive command warnings with directory-bound edit boundaries, coordinating checks before any tool execution.

Why do I need risk-mitigation automation for production environments?

Risk-mitigation automation is needed for production environments to reduce human error by warning before dangerous commands and blocking malicious or accidental edits beyond a protected directory boundary.