Block file edits outside a user-specified directory for the session.
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill freeze-yaugourt
Please help me install this Agent Skill. Skill: freeze Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/freeze Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill freeze-yaugourt
Restrict edits to a designated directory within the current session to prevent edits outside the boundary, useful during debugging or scoped changes.
Ask the user for a directory path and enable the freeze boundary for the current session.
High-intent search queries and answers about installing and using this skill.
You can restrict file edits to a directory by setting a session boundary that blocks Write and Edit operations outside the allowed path. This prevents unintended modifications during scoped changes.
A directory boundary is a user-specified path restriction that blocks edits to files outside that folder. It persists for the session and logs violations to maintain edit control.
You set up a PreToolUse hook by running a check-freeze.sh script that intercepts Edit and Write actions. The hook validates target file paths against a stored boundary and blocks violations.
Yes, you can persist a file edit boundary across a debugging session. The boundary is stored in a state file, ensuring edit restrictions remain active until the session ends.
Yes, the freeze boundary logs attempts to edit files outside the allowed path. When the PreToolUse hook detects an edit violation, it records the attempt before blocking the operation.
bizzybaeRestricts edits and writes to a defined directory boundary during a session.
Jesse-L-MRestrict file edits to a user-specified directory during a session.
joeylife94Restrict file edits to a specified directory for the session.
CarbeneAIRestrict file edits to a specified directory using a PreToolUse hook.
