guard

Restrict file edits to a specified directory with pre-edit scope checks.

58|6|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fagemx/gstack-game --skill guard-fagemx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/fagemx/gstack-game/tree/main/skills/guard
Command: npx skills add https://github.com/fagemx/gstack-game --skill guard-fagemx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full safety mode that prevents editing files outside a specified directory by combining destructive-command warnings with strict scope restrictions.

Core Features & Use Cases

  • Enforces edits only within a designated directory, blocking any changes outside the scope.
  • Provides warnings and override options to support development workflows while maintaining safety.
  • Useful during focused bug fixes, asset updates, or sensitive code maintenance.

Quick Start

Activate guard mode to restrict edits to the allowed directory.

Frequently Asked Questions about guard

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

FAQPage Schema
How do I restrict file edits to a specific directory during development?

To restrict file edits to a specific directory, you can use a scoped guard mode that enforces pre-edit scope checks and blocks unauthorized changes outside the allowed path. This prevents accidental modifications during focused bug fixes or asset updates.

What is scoped guard mode for safe filesystem edits?

Scoped guard mode is a safety mechanism that combines destructive-command warnings with strict directory restrictions to prevent editing files outside a designated scope. It ensures changes only occur within authorized boundaries during code maintenance.

Can I override scope restrictions if I need to edit files outside the allowed directory?

Yes, the scoped guard mode provides warnings and override options to support development workflows while maintaining safety. You can bypass the strict scope restrictions when necessary, though it actively blocks changes outside the allowed directory by default.

Does guard mode integrate with the gstack-game CLI for safe code maintenance?

Yes, scoped guard mode integrates directly with the gstack-game CLI to apply pre-edit scope checks and enforce safe editing workflows. This integration ensures filesystem edits remain confined to the specified directory during sensitive code maintenance.

When should I use directory scope restrictions for filesystem edits?

You should use directory scope restrictions during focused bug fixes, asset updates, or sensitive code maintenance where safe editing is essential. It prevents accidental or unauthorized changes by enforcing edits only within a designated directory scope.