gstack-freeze

Restrict Edit and Write operations to a designated directory path.

1|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-freeze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-freeze
Source: https://github.com/tan-yong-sheng/GrowChat/tree/main/.claude/skills/gstack-freeze
Command: npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-freeze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict Edits to a specific directory during a session to prevent accidental or unwanted changes outside the defined scope.

Core Features & Use Cases

  • Blocks Edit and Write outside the configured path to help debugging and scoped changes.
  • Allows safe testing by locking down edits to a single module or folder, reducing risk of collateral changes.
  • Use Case: during a debugging session, focus work on /src/utils without touching other parts of the repository.

Quick Start

Ask the user for a directory path to restrict edits to, then set the freeze boundary for that path.

Frequently Asked Questions about gstack-freeze

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

FAQPage Schema
How do I restrict edits to a specific directory during a debugging session?

To restrict edits to a specific directory, you can set a directory-scoped edit boundary that blocks Edit and Write operations outside the configured path. This prevents accidental changes to other parts of the repository during debugging.

What is directory freeze and how does it prevent scope creep?

Directory freeze is a mechanism that locks edits to a designated path, preventing scope creep by ensuring all modifications stay within the allowed folder. It operates via PreToolUse hooks that run a boundary-check script.

Can I lock down code changes to a single module for safe testing?

Yes, you can lock down code changes to a single module or folder to allow safe testing. This reduces the risk of collateral changes by blocking write operations outside the defined directory boundary.

How do I set a boundary for scoped changes in my repository?

You can set a boundary for scoped changes by providing a directory path to restrict edits to. The system then stores this boundary state for the session, ensuring all subsequent edits remain within the allowed path.

Does the edit boundary persist across multiple debugging sessions?

Yes, the edit boundary works across debugging sessions and code exploration. It stores the boundary state for the session, continuously ensuring all Edit and Write operations stay within the allowed path.

When should I use a directory-scoped edit restriction?

You should use directory-scoped edit restriction when you need to focus work on a specific folder like /src/utils without touching other parts of the repository. It is ideal for preventing unwanted changes during debugging or scoped modifications.