Block Edit and Write operations outside a chosen directory.
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill freeze-akiyoshi
Please help me install this Agent Skill. Skill: freeze Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/freeze Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill freeze-akiyoshi
Edits to files outside a defined directory can cause accidental changes during debugging or collaboration. This skill locks edits to a specified boundary to prevent unintended modifications.
Set the freeze boundary to a directory, then edits outside that path will be blocked for the current session.
High-intent search queries and answers about installing and using this skill.
To lock edits to a specific directory during debugging, you can set an editing boundary that blocks Edit and Write operations outside the chosen path for the current session.
Yes, you can restrict file modifications to a single project scope by setting a boundary path, which prevents accidental changes to files outside that directory.
An edit-lock prevents accidental changes during collaboration by monitoring Edit and Write operations and persisting the editing boundary in a state file for the session.
You can change or clear a directory freeze boundary using the provided controls to manage your session scope, removing the restriction when isolation is no longer needed.
A limitation of using a state file for workflow guardrails is that the edit-lock boundary is enforced for the current session only and does not provide persistent protection outside of it.
bizzybaeRestricts edits and writes to a defined directory boundary during a session.
KrismithReddy12Remove directory-level edit restrictions by deleting the freeze state file.
SakshamKandelRestrict Edit and Write tool calls to a user-specified directory for a session via a state file.
miko06Restricts file edits and writes to a designated directory during a session.
