skills.rest
robertzengcn
robertzengcnCOMMUNITY
Explore all skills by this author →
GitHub

freeze

Block Edit and Write operations outside a user-specified directory.

Updated Jul 21, 2025
Search Tags:#debugging#development workflow#code safety#scope control#file locking#edit restriction
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill freeze-robertzengcn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/freeze
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill freeze-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working on code or documents, it's easy to accidentally edit files outside the module or folder you're supposed to modify, leading to unintended bugs or wasted effort. This Skill eliminates that risk by blocking all Edit and Write operations outside a user-specified directory for the entire session.

Core Features & Use Cases

  • Scoped Edit Locking: Blocks all Edit and Write tool actions targeting files outside the configured directory, while leaving Read, Bash, Glob, and Grep operations unaffected.
  • Session Persistence: The freeze boundary stays active until you run the /unfreeze command or end the session, no need to re-configure it for every task.
  • Use Case: Ideal for debugging a single code module without risking changes to unrelated parts of the codebase, or when working on a scoped feature where you only want to modify files in one specific folder.

Quick Start

Ask the AI to restrict all file edits to the /src/features/authentication directory for this session.

Frequently Asked Questions about freeze

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

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

You can prevent accidental file edits by locking edit boundaries to a scoped directory, which blocks all Write and Edit operations outside the configured path while leaving Read and Bash commands unaffected.

What is scoped code editing and how does it protect my codebase?▼

Scoped code editing restricts file modifications to a single user-specified directory, protecting your codebase by blocking unintended edits to unrelated modules during targeted troubleshooting.

Can I restrict AI file modifications to a single module for an entire session?▼

Yes, you can restrict AI file modifications to a single module for an entire session using persistent edit locking. The boundary stays active until explicitly unfrozen or the session ends.

Does file locking affect Read, Bash, Glob, and Grep operations?▼

No, file locking does not affect Read, Bash, Glob, and Grep operations. The edit restriction only blocks Edit and Write tool actions targeting paths outside the configured freeze boundary.

How do I unlock file edits after scoping changes to a directory?▼

To unlock file edits after scoping changes to a directory, you run the unfreeze command. This removes the persistent session boundary and restores standard edit permissions across the workspace.

Related Skills

Explore More Software Engineering Skills→
muhammadhamad1104muhammadhamad1104

freeze

Lock file edits to a specified directory and validate paths before write operations.

Community
Basic
curielmccurielmc

unfreeze

Remove the freeze boundary to restore edit rights across all directories.

Community
Basic
mostafasudomostafasudo
3

document-release

Compare project documentation with the latest codebase and update files after release.

Community
Advanced
limzivectorlimzivector

freeze

Block file edits outside a designated directory during a session.

Community
Basic