maestro-guard

Configure directory-level write boundaries for workflow guard enforcement.

76|5|Updated Jul 7, 2026

Search Tags:#config management #project safety #directory permissions #path guard #write boundaries #workflow guard

Ready to run

npx skills add https://github.com/catlog22/pi-maestro-flow --skill maestro-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maestro-guard
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/maestro-guard
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill maestro-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you control where editing is allowed in a project, preventing accidental or unauthorized file writes during development workflows.

Core Features & Use Cases

Enable or disable path guard: Turn directory-level write protection on or off while preserving configuration state.
Manage allowed and denied paths: Add, remove, or clear boundary paths with normalized directory handling.
Validate enforcement readiness: Check whether the workflow-guard hook is active and warn when protection is configured but not enforced.
Use case: Use this Skill when you want to limit an AI assistant to specific folders such as source code, tests, or workflow files while keeping other areas protected.

Quick Start

Ask the assistant to check the current guard status and enable path protection for your project directories.

Frequently Asked Questions about maestro-guard

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

FAQPage Schema

How do I set directory-level write boundaries to restrict file edits in a coding project?▼

To set directory-level write boundaries, you configure allowed and denied paths within a workflow guard, which normalizes directory handling and enforces permission-controlled editing across your project.

What is project path guard and how does it protect specific directories?▼

Project path guard protects directories by applying non-destructive state changes to configuration files, validating hook presence, and warning when protection is configured but not actively enforced.

How do I limit an AI assistant to only edit specific folders like source code and tests?▼

By managing allowed and denied paths in the guard configuration, you can scope AI assistant edits to specific folders while applying path normalization to ensure consistent directory handling.

Can I disable path protection temporarily without losing my current directory permissions configuration?▼

The guard supports enabling or disabling path protection while preserving configuration state, so you can toggle enforcement without clearing your established allowed and denied path boundaries.

Why does my path guard configuration warn that protection is not enforced?▼

This warning occurs during enforcement readiness validation when the workflow-guard hook is inactive, indicating that write boundaries are configured but lack active hook presence to enforce them.

Does the workflow guard support non-destructive config changes when updating denied paths?▼

The guard requires config-only mutation and non-destructive state changes when managing denied paths, ensuring path normalization and boundary updates occur without modifying existing project files.