Agent skill
freeze
Restrict file edits to one directory. Prevents accidental changes outside scope while debugging or working on a focused task. Use when you want to scope edits to a specific module or directory.
Install this agent skill to your Project
npx add-skill https://github.com/DenchHQ/DenchClaw/tree/main/skills/gstack/freeze
SKILL.md
Freeze — Scope Lock
Restrict all file edits to a single directory. Prevents accidental changes to unrelated code while debugging or making focused changes.
Related skills: unfreeze | guard | careful | investigate
Activation
When the user says "freeze to [directory]" or when investigate auto-locks scope:
- Record the allowed directory
- Before every file edit, check if the target file is within the allowed directory
- If outside: block the edit and explain why
Behavior
🔒 FREEZE ACTIVE: edits restricted to src/auth/
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Allowed
- Any file under the frozen directory
- Reading files anywhere (read-only is always allowed)
Blocked
- Editing files outside the frozen directory
- Creating new files outside the frozen directory
When Blocked
⛔ EDIT BLOCKED: src/api/handler.ts is outside the freeze boundary (src/auth/)
Run /unfreeze to remove the restriction, or explain why this file needs to change.
Use Cases
- Debugging: Lock to the buggy module to prevent scope creep
- Focused refactoring: Only touch the files you're refactoring
- Code review fixes: Only modify files in the PR
Use unfreeze to remove the restriction.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
dench-integrations
Connected app integration recipes for Dench Integrations (Gmail, Slack, GitHub, Notion, Google Calendar, Linear, Stripe, YouTube, and 500+ more)
gstack-workflow
Structured AI-assisted development workflow with specialist roles — Think, Plan, Build, Review, Test, Ship, Reflect. Adapted from garrytan/gstack (MIT).
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises. Four modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION. Use when reviewing strategy, questioning scope, or before engineering review.
investigate
Systematic root-cause debugging. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause investigation first. Use when debugging errors, unexpected behavior, or troubleshooting.
design-consultation
Build a complete design system from scratch. Research the landscape, propose safe choices AND creative risks, generate DESIGN.md. Use when creating a new design system or establishing design foundations for a project.
land-and-deploy
Merge the PR, wait for CI and deploy, verify production health. Takes over after ship. One command from "approved" to "verified in production."
Didn't find tool you were looking for?