冻结

其他 社区 v0.1.0

技能解读

设计思路

freeze 是 gstack 的「编辑边界锁」——告诉 hook:从现在起,Edit / Write 工具只能改某个目录里的文件,超出边界直接 deny(不是 warn)。设计目的是给 agent 一个「围栏」,让它明确知道哪些文件是这个 task 该碰的,避免误改不相关代码。注意作者明确说这不是安全边界——bash sed 这种命令仍然能在围栏外动文件,但能挡住 90% 的手滑误改。

Setup 流程

# 1. 用 AskUserQuestion 让用户输入要锁的目录(文本输入,不是单选)
# 2. 解析为绝对路径
FREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)

# 3. 加尾斜杠避免 /src 误匹配 /src-old
FREEZE_DIR="${FREEZE_DIR%/}/"

# 4. 写入 gstack state 文件
eval "$(~/.claude/skills/gstack/bin/gstack-paths)"
STATE_DIR="$GSTACK_STATE_ROOT"
mkdir -p "$STATE_DIR"
echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"

设置完后会回执:「Edits are now restricted to <path>/. Any Edit or Write outside this directory will be blocked. To change the boundary, run /freeze again. To remove it, run /unfreeze or end the session.」

工作机制

hook 读 Edit/Write 工具调用里的 file_path,检查它是否以 freeze directory 开头——不是就返回 permissionDecision: "deny" 直接拦截。

关键边界条件

  • 尾斜杠不可省——防 /src 误匹配 /src-old。
  • 只管 Edit / Write——Read / Bash / Glob / Grep 不受影响。
  • 不是安全边界——bash 里的 sed / mv 仍可绕过。
  • session 范围——重开会话就失效,或显式 /unfreeze 解除。

适合谁

  • 让 agent 改某个模块时希望 sandbox 化的工程师
  • 重构 / 整理 monorepo 单包时怕动到别的包
  • 给新人用 agent 时多一道防误改

不适合

  • 任务本身需要跨目录改动(big refactor)——围栏会一直拦
  • 已经有 git pre-commit hook 防御足够时

配套

unfreeze(解除)、careful(命令级危险拦截)、git-guardrails-claude-code(git 级 PreToolUse 拦截)一起组成多层防护。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
通用
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
92 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@garrytan · v0.1.0 · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
macOS · Linux · Windows
运行环境要求
Bun
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->


## When to invoke this skill

Blocks Edit and
Write outside the allowed path. Use when debugging to prevent accidentally
"fixing" unrelated code, or when you want to scope changes to one module.
Use when asked to "freeze", "restrict edits", "only edit this folder",
or "lock down edits".

# /freeze — Restrict Edits to a Directory

Lock file edits to a specific directory. Any Edit or Write operation targeting
a file outside the allowed path will be **blocked** (not just warned).

```bash
mkdir -p ~/.gstack/analytics
echo '{"skill":"freeze","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/analytics/skill-usage.jsonl 2>/dev/null || true
```

## Setup

Ask the user which directory to restrict edits to. Use AskUserQuestion:

- Question: "Which directory should I restrict edits to? Files outside this path will be blocked from editing."
- Text input (not multiple choice) — the user types a path.

Once the user provides a directory path:

1. Resolve it to an absolute path:
```bash
FREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)
echo "$FREEZE_DIR"
```

2. Ensure trailing slash and save to the freeze state file:
```bash
FREEZE_DIR="${FREEZE_DIR%/}/"
eval "$(~/.claude/skills/gstack/bin/gstack-paths)"
STATE_DIR="$GSTACK_STATE_ROOT"
mkdir -p "$STATE_DIR"
echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"
echo "Freeze boundary set: $FREEZE_DIR"
```

Tell the user: "Edits are now restricted to `<path>/`. Any Edit or Write
outside this directory will be blocked. To change the boundary, run `/freeze`
again. To remove it, run `/unfreeze` or end the session."

## How it works

The hook reads `file_path` from the Edit/Write tool input JSON (shared
real-JSON extractor with /careful — one copy, sourced by both hooks), then
checks whether the path starts with the freeze directory. If not, it returns a
`hookSpecificOutput` payload with `permissionDecision: "deny"` to block the
operation (nested under `hookSpecificOutput` — Claude Code ignores a top-level
`permissionDecision`).

Polarity is fail-closed: a tool payload the hook cannot parse is DENIED, not
allowed — a boundary that fails open is not a boundary. A payload that parses
but has no `file_path` (a non-file tool) is allowed. Symlinks are resolved
through their FINAL component, so an in-boundary symlink pointing outside the
boundary is checked against its target.

The freeze boundary persists for the session via the state file. The hook
script reads it on every Edit/Write invocation. Boundaries containing spaces
are supported.

## Notes

- The trailing `/` on the freeze directory prevents `/src` from matching `/src-old`
- Freeze applies to Edit and Write tools only — Read, Bash, Glob, Grep are unaffected
- This prevents accidental edits, not a security boundary — Bash commands like `sed` can still modify files outside the boundary
- To deactivate, run `/unfreeze` or end the conversation

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。