freeze

Restricts edits and writes to a defined directory boundary during a session.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/bizzybae/qstack --skill freeze-bizzybae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/bizzybae/qstack/tree/main/gstack-original/freeze
Command: npx skills add https://github.com/bizzybae/qstack --skill freeze-bizzybae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits".

Core Features & Use Cases

  • Enforces a per-session edit boundary to prevent edits outside a chosen directory.
  • Validates and normalizes the target path, persisting the boundary for the session.
  • Logs boundary-denial events for auditing while keeping local scope.

Quick Start

Ask the user which directory to restrict edits to, and set that absolute path as the freeze boundary.

Frequently Asked Questions about freeze

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 a coding session?

To restrict file edits to a specific directory, you can set an absolute path as a session-scoped boundary. This blocks all Edit and Write operations outside the allowed folder, preventing accidental modifications to unrelated code.

Why would I need to lock down edits to a single directory boundary?

Locking down edits to a directory boundary is useful when debugging or scoping changes to one module. It prevents the system from accidentally fixing or rewriting unrelated code outside your target folder during that active session.

How do I audit blocked file writes when enforcing a directory boundary?

When a directory boundary is enforced, denied edit attempts are logged locally for auditing. The system validates and normalizes the target path, records the boundary-denial event, and keeps the audit scope strictly local.

Can I change the directory boundary once it has been set for the current session?

The directory boundary is persisted in a session state file, meaning it remains active for the duration of the session. You establish the boundary by providing an absolute path, and it continues to block outside edits until the session concludes.

Does restricting edits to a directory boundary require any special dependencies?

No dependencies are required to restrict edits to a directory boundary. The feature works standalone by applying validation to all Edit and Write operations within the active session using your provided path.

What happens if a write operation targets a path outside the freeze boundary?

If a write operation targets a path outside the freeze boundary, the operation is blocked. The system normalizes the requested path, compares it against the stored session boundary, and logs the denial locally for auditing.