freeze

Restrict file edits and writes to a configured directory boundary.

Updated Mar 27, 2026

Search Tags:#project management #restriction #file security #edit scope #development safety

Ready to run

npx skills add https://github.com/BaGyun0107/harness-starterkit --skill freeze-bagyun0107

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/BaGyun0107/harness-starterkit/tree/main/.agents/skills/gstack-freeze
Command: npx skills add https://github.com/BaGyun0107/harness-starterkit --skill freeze-bagyun0107

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents accidental or unauthorized modifications by restricting file edits to a designated directory, ensuring safer code management.

Core Features & Use Cases

Scoped Editing: Limit file changes within a specified directory during development or debugging sessions.
Safety Enhancement: Avoid unintended modifications outside critical areas when collaborating or debugging.
Use Case: Developers want to lock editing permissions to a particular folder, such as 'src/moduleA', avoiding changes to other parts of the project.

Quick Start

Ask the user which directory should be restricted and confirm the boundary before applying the restriction.

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 during a development session, you can set a directory boundary that verifies file paths before allowing any modifications. This prevents unauthorized changes outside the set scope.

How does setting a directory boundary improve project file security?▼

Setting a directory boundary improves project file security by applying restrictions to file edit and write operations. It uses environment files to store the boundary path and blocks any modifications outside that designated scope.

Can I lock editing permissions to a single folder like 'src/moduleA' to protect the rest of the project?▼

Yes, you can lock editing permissions to a specific folder like 'src/moduleA'. By confirming the boundary path before applying the restriction, you ensure changes are confined strictly to that module, safeguarding other project areas.

What is the best way to prevent accidental code modifications when debugging?▼

The best way to prevent accidental code modifications when debugging is to implement session-based edit restrictions. This confines your file writes to a designated directory, enhancing development safety by avoiding unintended changes.

Do I need to configure environment files to enforce edit scope limitations?▼

Yes, you need to configure environment files to enforce edit scope limitations. The system uses these environment files to store the designated boundary path, which is then verified against file paths before any edit operations are permitted.