freeze

Enforce a session-scoped directory boundary blocking Edit and Write operations.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/nocnocgroup/gstack --skill freeze-nocnocgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/nocnocgroup/gstack/tree/main/freeze
Command: npx skills add https://github.com/nocnocgroup/gstack --skill freeze-nocnocgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents edits spilling outside a defined directory, enabling safe debugging and scoped experimentation without affecting unrelated code.

Core Features & Use Cases

  • Boundary enforcement: Edits and writes outside the configured directory are blocked in the current session.
  • Session-scoped control: The boundary lasts for the active session and can be reset with /unfreeze.
  • Audit-ready: Violations are logged for review and compliance.

Quick Start

Provide the directory path to freeze, then activate the boundary with /freeze.

Frequently Asked Questions about freeze

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

FAQPage Schema
How do I prevent edits outside a specific directory during a debugging session?▼

A directory boundary prevents edits outside a specific directory during debugging sessions by enforcing a runtime boundary. It blocks Edit and Write operations from leaking into unrelated modules, ensuring safe and scoped experimentation.

How does a PreToolUse hook enforce edit control for scoped debugging?▼

A PreToolUse hook enforces edit control by intercepting tool calls and denying Write and Edit operations that target paths outside a defined directory. This stateful boundary is stored locally, preventing unauthorized modifications during active sessions.

Can I reset directory boundaries and unfreeze edits mid-session?▼

Yes, you can reset directory boundaries and unfreeze edits mid-session. The boundary is session-scoped, meaning it lasts for the active session and can be easily removed or reset using the /unfreeze command when you need broader access.

What is the best way to audit directory boundary violations in my codebase?▼

The best way to audit directory boundary violations is to use a boundary enforcement tool that logs denied edit attempts. This provides an audit-ready record of all out-of-bound operations for review and compliance tracking.

Do I need any external dependencies to lock edits to a single directory?▼

No external dependencies are needed to lock edits to a single directory. The boundary is enforced using a local stateful file and a PreToolUse hook, meaning it operates independently within your current environment without requiring additional packages.