Index of every page on this site: llms.txt
All skills
garrytan avatar

/unfreeze

@8586794 official
by Garry Tangarrytan/gstack142k stars
20,987
Run it yourself

Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use for: unfreeze edits, unlock all directories. (gstack)

Requires /freeze
Use this Skill: https://skilld.dev/gh/garrytan/gstack/unfreeze

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈38 tokens for metadata: the name and description. ≈326 when used: this file.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈151 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs -->

/unfreeze — Clear Freeze Boundary

Remove the edit restriction set by /freeze, allowing edits to all directories.

GSTACK_STATE_ROOT=$(~/.claude/skills/gstack/bin/gstack-paths --get GSTACK_STATE_ROOT); : "${GSTACK_STATE_ROOT:?gstack-paths failed; reinstall with ./setup or /gstack-upgrade}"
mkdir -p "$GSTACK_STATE_ROOT"/analytics
echo '{"skill":"unfreeze","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}'  >> "$GSTACK_STATE_ROOT"/analytics/skill-usage.jsonl 2>/dev/null || true

Clear the boundary

bash "$HOME/.claude/skills/gstack/freeze/bin/freeze-state.sh" clear

This is explicit user-requested removal, not investigation cleanup. The shared writer serializes it with acquisition, replacement and owner-checked release. On FREEZE_BUSY or unexpected state, leave everything untouched and report recovery; never delete state or a possibly active mutation lock directly.

Tell the user the result. Note that /freeze hooks are still registered for the session — they will just allow everything since no state file exists. To re-freeze, run /freeze again.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill manages local edit restrictions for the gstack toolset and logs usage data to a local file. No security risks were identified.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: LOW · No issues

Signed by skilld at 8586794. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
What it can do
Runs commands Reads files
version
0.1.0
triggers
[
  "unfreeze edits",
  "unlock all directories",
  "remove edit restrictions"
]
All 2 allowed tools
BashRead
  • gstack
  • bash
  • freeze
  • edit-scope
  • session-state
  • directory-restrictions

README badge

README badge for garrytan/gstack/unfreeze

Removes the edit restriction set by /freeze, restoring the ability to edit all directories in the session. Part of the gstack workflow for managing edit scope boundaries.

Generated from the current SKILL.md.

What does this skill do?
Clears the freeze boundary set by /freeze, allowing edits to all directories again within the same gstack session.
Do I need to end my session to use this?
No. This skill removes edit restrictions without ending the session, so you can continue working with expanded edit scope.
Will /freeze hooks still be active after running unfreeze?
Yes. The /freeze hooks remain registered for the session but will allow all edits since the freeze state file is deleted. Running /freeze again will re-enable restrictions.
What happens if no freeze boundary is currently set?
The skill will report that no freeze boundary was set and make no changes.

Generated from the current SKILL.md. These answers refresh after source changes.