freeze

Restricts Edit and Write operations to a specified directory for the session.

Updated May 15, 2026
One-click install
npx skills add https://github.com/tgmarinho/canetaco --skill freeze-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/tgmarinho/canetaco/tree/main/.claude/skills/freeze
Command: npx skills add https://github.com/tgmarinho/canetaco --skill freeze-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging or working on a focused task, AI-assisted edits can accidentally modify unrelated files across the repository. This Skill prevents that by blocking any Edit or Write operation outside a directory you choose, keeping changes scoped to one module. ## Core Features & Use Cases - Directory-Scoped Editing: Set a freeze boundary so Edit and Write tools are denied for any file outside the allowed path. - Hook-Based Enforcement: Uses PreToolUse hooks on Edit and Write that run a check script and return a deny decision for out-of-bounds paths. - Session Persistence: The freeze boundary is stored in a state file and enforced on every edit until you run /unfreeze or end the session. - Use Case: While debugging a bug in the billing module, freeze edits to the billing directory so no unrelated code gets accidentally "fixed" during the investigation. ## Quick Start Ask the assistant to freeze edits to the directory you are working in, for example by saying "freeze edits to src/billing".

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 one directory in a session?

Run the freeze command and provide the target directory when prompted. The path is resolved to an absolute path, saved to a state file, and every subsequent Edit or Write outside that directory is blocked until you unfreeze or end the session.

How do I remove or change the edit restriction?

Run /unfreeze to remove the boundary entirely, or run /freeze again to set a new directory. Ending the conversation also clears the restriction since the boundary only persists for the session.

Does the freeze boundary block all file modifications?

No. It only blocks the Edit and Write tools. Read, Bash, Glob, and Grep are unaffected, and shell commands like sed can still modify files outside the boundary, so it prevents accidental edits rather than acting as a security boundary.

Why does the freeze directory need a trailing slash?

The trailing slash ensures prefix matching is exact, so a freeze on /src does not accidentally allow edits in a sibling directory like /src-old. The setup step normalizes the path before saving it.

When should I use directory-scoped editing?

Use it when debugging a specific module and you want to prevent accidental fixes to unrelated code, or when a task should only touch one folder. It keeps the change surface small and reviewable.