freeze

Restrict Edit and Write operations to a user-defined directory boundary.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill freeze-zaeem-rafiq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/zaeem-rafiq/tatheer-swift-sdk/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill freeze-zaeem-rafiq

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 to prevent accidental or unauthorized modifications.

Core Features & Use Cases

  • Freeze a boundary by selecting and persisting an absolute directory path for the session.
  • Enforce boundary checks on Edit and Write operations while leaving Read unrestricted, with clear denial messages and basic analytics logging.
  • Use during debugging or when you want to scope changes to a single module to avoid accidental global edits.

Quick Start

Set a directory as the freeze boundary and start the session to restrict edits within that path.

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

You can restrict file edits to a specific directory by setting an absolute path as a boundary. The skill blocks Write and Edit operations outside that path, preventing unauthorized modifications while allowing Read operations to continue.

Can I still read files outside the enforced edit boundary?

Yes, reading files outside the enforced edit boundary remains fully unrestricted. The boundary check only applies to Write and Edit operations, allowing you to reference external code without modifying it.

How do I enforce a directory boundary for debugging without altering global files?

To enforce a directory boundary for debugging, define an absolute path in the state file. This scopes all Write and Edit operations to that single module, ensuring global files remain untouched while you debug.

Does the edit boundary tool work without external dependencies?

Yes, the edit boundary tool works without external dependencies. It operates independently by reading the defined path from a state file and evaluating operations against that directory boundary.

What happens when a Write operation targets a path outside the frozen boundary?

When a Write operation targets a path outside the frozen boundary, the system returns a clear denial message. This blocks the unauthorized edit and logs the event in basic analytics for review.