What problem does it solve?
This Skill solves the problem of being stuck in a restricted editing scope after a freeze boundary has been set, preventing the assistant from modifying files outside the initially allowed directories.
Core Features & Use Cases
- Clears the freeze boundary: Removes the saved boundary state so edits are allowed across all directories.
- Supports manual control: Designed as a manual trigger only, invoked when the user explicitly types /unfreeze.
- Session-safe behavior: Keeps session hooks registered from /freeze, but with the state cleared it effectively unlocks edits for the remainder of the session.
Use it when you are asked to “unfreeze”, “unlock edits”, “remove freeze”, or “allow all edits”, such as when an iterative review starts narrow but later requires broader changes across the repository.
Quick Start
Ask the assistant to run /unfreeze to clear the freeze boundary and allow edits everywhere again.