freeze

Restrict Edit and Write operations to a user-defined directory during a session.

1|2|Updated Jan 4, 2024
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill freeze-nakmiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/freeze
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill freeze-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session to prevent accidental or undesired edits outside the scope. This is especially useful during debugging or when you want to limit changes to a single module.

Core Features & Use Cases

  • Blocks Edit and Write outside the allowed path to contain changes within a designated folder.
  • Useful during debugging to prevent unintended modifications to unrelated code.
  • Supports persistent boundary state across the session for consistent enforcement.

Quick Start

Ask the user which directory to freeze edits to, and confirm the boundary before enabling 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?

You can restrict file edits by locking Edit and Write operations to a single user-defined directory, ensuring changes stay within that boundary and preventing accidental modifications to unrelated code.

How does directory scoping prevent unintended modifications during debugging?

Directory scoping enforces a configurable boundary on file edits, containing all changes within a designated folder to prevent unintended modifications to unrelated code while you debug a specific module.

Can I maintain a persistent edit boundary across an entire session?

Yes, you can maintain a persistent edit boundary across an entire session, which provides consistent enforcement of the directory scope until the restriction is no longer needed.

What happens if the edit boundary is unset or mis-specified?

If the edit boundary is unset or mis-specified, the restriction applies safe fallbacks to handle the error, ensuring that file edits do not proceed with an ambiguous or invalid directory scope.

Do I need to configure a pretool hook to block Write operations outside a directory?

You do not need to manually configure a pretool hook, as the restriction automatically applies to Edit and Write operations to block any file changes attempted outside the allowed directory path.