Skills › gstack › unfreeze

unfreeze

skill · 36 lines · MIT · unfreeze/SKILL.md

The facts

Its description

Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack) Triggers: unfreeze edits; unlock all directories; remove edit restrictions

The description the agent reads to decide when to use it. Phrases the author says should start it.

From its settingsline 4 line 5

When it starts

A short cleanup command: the agent picks it when someone wants the directory-scoped edit restriction from /freeze lifted so edits are allowed everywhere again. It is a one-step teardown, not an investigation or review.

Things a person might say (the model's guesses)

“unfreeze”
“unlock all directories”
“remove the edit restrictions”

A model's summary of when it is used.

A model's reading

Tools it may use, or may not

allowed-tools: Bash, Read

Tools it may use while it runs without asking you first.

From its settingsline 9

Runs scripts

bin/gstack-paths, bin/freeze-state.sh

Scripts the text names. Found by matching words, so treat them as pointers.

Found by matching wordsline 21 line 29

What it leads to

hands off to freeze line 36
calls gstack-upgrade only if gstack-paths fails line 21

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

freeze hands off to this freeze, line 64
gstack hands off to this PROACTIVE all, or user names it gstack, line 223
guard hands off to this to remove the persistent edit boundary guard, line 79

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

What leads to it

investigate hands off to this investigate, line 278

Other skills that hand off to this one, call it, require it or offer it instead, found by matching their names, so treat them as pointers.

Found by matching words

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

Other settings

version: 0.1.0

More settings at the top of the file, shown as written.

From its settingsline 3

The text

Runs code Names a skill

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---

2name: unfreeze

3version: 0.1.0

4description: Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)

5triggers:

6 - unfreeze edits

7 - unlock all directories

8 - remove edit restrictions

9allowed-tools:

10 - Bash

11 - Read

12---

13

14

16# /unfreeze — Clear Freeze Boundary

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

20```bash

21GSTACK_STATE_ROOT=$(~/.claude/skills/gstack/bin/gstack-paths --get GSTACK_STATE_ROOT); : "${GSTACK_STATE_ROOT:?gstack-paths failed; reinstall with ./setup or /gstack-upgrade}"

22mkdir -p "$GSTACK_STATE_ROOT"/analytics

23echo '{"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

24```

/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

Raw lines 1 to 25

Names a skill freeze :18

Runs code bin/gstack-paths :21

Names a skill gstack-upgrade :21

26## Clear the boundary

28```bash

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

30```

32This 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.

34Tell the user the result. Note that `/freeze` hooks are still registered for the

35session — they will just allow everything since no state file exists. To re-freeze,

36run `/freeze` again.

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.

Raw lines 26 to 36

Runs code bin/freeze-state.sh :29

Names a skill freeze :34

From garrytan/gstack at 3f79d81, 2026-11-01. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.