One-click install
npx skills add https://github.com/reomgit/appstore-ss-downloader --skill freeze-reomgit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/reomgit/appstore-ss-downloader/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/reomgit/appstore-ss-downloader --skill freeze-reomgit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents accidental edits to files outside a specified directory, allowing users to focus on a particular codebase or module during development.

Core Features & Use Cases

  • Directory Locking: Lock file edits to a specific directory, blocking any attempts to edit files outside of it.
  • Session Persistence: The freeze boundary persists for the session, ensuring consistent protection against unintended edits.
  • Use Case: When debugging, this Skill can be used to prevent accidentally modifying unrelated code, or to scope changes to one specific directory or module.

Quick Start

Run /freeze to set the directory where you want to restrict edits. Any attempt to edit a file outside this directory will be blocked.

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?

Restricting file edits to a specific directory involves setting a boundary that blocks any modifications to files outside the defined scope. You can activate this directory locking mechanism by running the /freeze command to establish the session restriction.

How does directory locking prevent accidental modifications to unrelated code?

Directory locking prevents accidental modifications by enforcing a boundary check before any file editing operations occur. This ensures that attempts to modify files outside the locked directory are blocked, keeping your changes scoped to a single module or codebase.

Can I use bash scripts to lock file edits to a single module while debugging?

Yes, you can use bash scripts to lock file edits to a single module while debugging. The skill requires Bash scripts for enforcing the boundary check before file editing operations, ensuring consistent protection throughout your session.

What is the best way to scope code changes to one directory and prevent unintended edits?

Scoping code changes to one directory is best achieved by setting a session persistent boundary that restricts edits to a defined scope. Running /freeze locks file edits to a specific directory, preventing any unintended edits to unrelated files.

Does the directory restriction persist for the entire session or only for a single edit?

The directory restriction persists for the entire session, ensuring consistent protection against unintended edits. The freeze boundary remains active until the session ends, blocking any attempts to edit files outside the specified directory throughout your work.