freeze

Restricts file edits and writes to a designated directory during a session.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/miko06/MedicineSimulator --skill freeze-miko06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/miko06/MedicineSimulator/tree/main/.opencode/skills/gstack-freeze
Command: npx skills add https://github.com/miko06/MedicineSimulator --skill freeze-miko06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that file edits are confined to a designated directory, preventing accidental changes to unrelated files during debugging or targeted development.

Core Features & Use Cases

  • Directory Locking: Locks editing scope to a specific directory.
  • Prevents Unwanted Edits: Blocks Edit and Write operations outside the allowed path.
  • Use Case: Ideal for when you need to "freeze" changes to a particular module, ensuring that accidental fixes don't affect unrelated parts of the codebase.

Quick Start

Run the command: /freeze /path/to/directory.

Frequently Asked Questions about freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restrict file edits to a specific directory during a development session?

To restrict file edits to a specific directory, you can use a directory locking script that enforces session scoping, preventing any Edit or Write operations outside the designated path.

Why do my debugging changes accidentally affect unrelated files in my codebase?

Accidental fixes affect unrelated files when editing scope is unrestricted. Applying a directory lock prevents unwanted edits by strictly confining modifications to a targeted module.

Can I lock file editing scope to a single folder using Bash?

Yes, you can lock file editing scope using Bash and basic scripting capabilities, which blocks edit and write operations outside the allowed directory path for the session.

What is the best way to prevent accidental code modifications outside a target module?

The best way to prevent accidental code modifications is applying directory locking, which freezes changes to a particular module and blocks write operations to unrelated parts.

How do I freeze code changes to a particular directory to ensure development safety?

To freeze code changes and ensure development safety, execute a directory lock command that scopes file edits exclusively to the specified path, blocking all external modifications.