メニュー
Block Edit/Write outside one session directory to contain debugging or parallel agents. Triggers "freeze edits", "lock editing scope", "restrict edits to", "only edit this folder", "unfreeze".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/darkroomengineering/cc-settings --skill freezeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Lighthouse audit + improvement loop until targets met. Triggers "lighthouse", "page speed", "improve scores", "LCP", "CLS", "INP", "core web vitals". Repo-wide perf audits ("perf audit") go to /audit performance mode instead.
Eight audit modes (codebase — owns "audit the codebase" — docs/process, performance, threat-model, motion, SEO, debt). Triggers "nuclear review", "whole codebase review", "adversarial audit", "fable audit", "correctness audit", "audit the docs", "doc drift", "process audit", "perf audit", "why is it slow", "bundle audit", "threat model", "attack surface", "motion audit", "seo audit", "aeo", "llms.txt", "debt ledger", "shortcut ledger". Single-page CWV routes to /lighthouse.
Parallel divergent ideation — framed generators, then a critic scores, clusters, deepens top 3. Triggers "/adhd", "brainstorm", "ideate", "widen the option space", fuzzy design/debugging. Skip lookups, syntax, known-root-cause bugs.
SKILL.md を表示中
| name | freeze |
| argument-hint | [set|off|status] [dir] |
| description | Block Edit/Write outside one session directory to contain debugging or parallel agents. Triggers "freeze edits", "lock editing scope", "restrict edits to", "only edit this folder", "unfreeze". |
| context | main |
| allowed-tools | ["Bash","AskUserQuestion"] |
Stop here in standalone Codex. The plugin does not install a freeze guard for
apply_patch, so this skill cannot enforce an edit boundary. Do not write
freeze state or claim a directory is locked. Tell the user the operation is
unsupported and use explicit file ownership as a convention only if they want
to continue without enforcement.
The remaining workflow is Claude-only.
Restrict Edit and Write to a single directory. Any edit targeting a file outside the boundary is blocked by the freeze-guard PreToolUse hook. State persists in ~/.claude/tmp/freeze.json, tagged with the session that set it — a freeze forgotten from a different session or project self-heals away automatically instead of blocking the next session's edits.
Note: notebook edits (NotebookEdit) and shell writes (Bash) are not gated — the boundary covers the file-editing tools only.
If the user named a directory, use it. Otherwise ask which directory to lock to (AskUserQuestion, free-text path). Then run, substituting the chosen path for PATH:
bun ~/.claude/src/scripts/freeze.ts set "PATH"
Confirm to the user that edits are now restricted to that path, and that they can lift it any time with "unfreeze".
bun ~/.claude/src/scripts/freeze.ts off
bun ~/.claude/src/scripts/freeze.ts status