Blocks Edit and Write operations targeting files outside a user-specified directory boundary.
npx skills add https://github.com/bobbo01/B2BPlatform --skill freeze-bobbo01
Please help me install this Agent Skill. Skill: freeze Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack-freeze Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill freeze-bobbo01
High-intent search queries and answers about installing and using this skill.
Run the freeze command and provide the directory path when prompted. The skill resolves it to an absolute path, saves it to a state file, and a hook then blocks every Edit or Write call targeting files outside that path for the rest of the session.
Run /unfreeze or end the session to remove the restriction entirely. To change the boundary to a different directory, run /freeze again and provide the new path, which overwrites the saved state file.
No. The freeze hook only intercepts Edit and Write tool calls. Read, Bash, Glob, and Grep are unaffected, so shell commands like sed can still modify files outside the boundary. It prevents accidental edits, not a security boundary.
The trailing slash ensures prefix matching is exact at directory boundaries. Without it, a freeze on /src would also match a sibling directory like /src-old, incorrectly allowing edits there.
The boundary is stored in a state file under the plugin data directory and is read on every Edit or Write invocation. It is intended to last for the session and is cleared by running /unfreeze or ending the conversation.
jerrywu001Restrict file edits to a user-defined directory during debugging.
AZANIRAnalyze git diffs and commit history to recommend tests for execution, update, or creation.
notqueExplore codebases with read-only commands and report findings.
open-octoIsolate experimental code changes in a disposable Git worktree.
