Block file edits outside a configured directory during debugging sessions.
npx skills add https://github.com/TobiasPerry/aws-hackathon --skill freeze-tobiasperry
Please help me install this Agent Skill. Skill: freeze Source: https://github.com/TobiasPerry/aws-hackathon/tree/main/.claude/skills/gstack/freeze Command: npx skills add https://github.com/TobiasPerry/aws-hackathon --skill freeze-tobiasperry
Blocking edits outside a configured directory during debugging sessions saves time and prevents drift.
Ask the user to specify a directory, then apply and persist the freeze boundary for the current session.
High-intent search queries and answers about installing and using this skill.
To prevent file edits outside a specific directory during debugging, you can apply a freeze boundary that restricts Write and Edit operations to a configured path, blocking any out-of-bounds modifications.
Directory freeze enforcement is a safety mechanism that scopes edits to a single configured boundary, preventing unintended changes and drift across your project during a development session.
To set up a session-wide directory boundary, specify the target directory to apply the freeze. The boundary is loaded at runtime and persists across the session using a minimal state file.
Yes, the freeze boundary applies to both Edit and Write operations. A pre-tool-check script enforces the boundary and denies any actions attempted outside the allowed directory path.
Yes, you can use directory scoping tools to lock changes to a single module folder. When debugging a module, this prevents unintended modifications elsewhere in the project.
VertaKhanRestrict file edits to a designated directory for the current session.
GhostOf0daysExecute deep learning alpha workflows with parameter bounds and drift monitoring.
CarbeneAIBlock destructive shell commands and restrict file edits to a specified directory.
26mitch26Restrict file edits to a designated directory for a session.
