One-click install
npx skills add https://github.com/Dragoon0x/dragoon-skills --skill freeze-dragoon0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Dragoon0x/dragoon-skills/tree/main/skills/freeze
Command: npx skills add https://github.com/Dragoon0x/dragoon-skills --skill freeze-dragoon0x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When working on codebase refactors or onboarding new contributors, it is common to accidentally edit legacy or out-of-scope directories, leading to unintended changes and costly rework. This Skill eliminates that risk by letting you explicitly mark specific directories as off-limits to edits.

Core Features & Use Cases

  • Frozen Path Management: Add, remove, and list restricted directories, with all changes stored in a central .dragoon/freeze.json manifest for consistent access across workflows.
  • Git Pre-Commit Hook Enforcement: Optionally generate and install a pre-commit hook that automatically fails commits if any frozen path is modified, acting as a soft guardrail for team collaboration.
  • CI-Compatible Violation Checks: Run a dedicated check command in continuous integration pipelines to catch attempts to modify frozen paths before code is merged. Common use cases include isolating refactor work to a single module without touching legacy code, locking legacy directories that should never be modified, and limiting new contributors' edit scope to their assigned tasks.

Quick Start

Use the freeze skill to add the src/legacy directory to the frozen paths list and install the pre-commit hook to block all edits to that directory.

Frequently Asked Questions about freeze

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

FAQPage Schema
How do I prevent accidental edits to legacy directories during a codebase refactor?

You can prevent accidental edits to specific directories during a codebase refactor by freezing paths in a central manifest and optionally installing a git pre-commit hook to block commits that modify restricted paths.

How do I restrict new contributors from modifying out-of-scope directories?

To restrict new contributors from modifying out-of-scope directories, freeze those paths and enforce the boundaries using a git pre-commit hook or a dedicated CI-compatible check command that catches unauthorized modifications before merging.

Can I block git commits that modify specific directory paths?

Yes, you can block git commits that modify specific directory paths by generating and installing a git pre-commit hook that automatically fails any commit attempting to modify a frozen path listed in your manifest.

How do I check for frozen path violations in a continuous integration pipeline?

You can check for frozen path violations in a continuous integration pipeline by running a dedicated CI-compatible check command that detects attempts to modify restricted paths before code is merged into the shared codebase.

Where are frozen directory paths stored for consistent access across workflows?

Frozen directory paths are stored in a central .dragoon/freeze.json manifest, ensuring consistent access and management across different contributor onboarding and refactoring workflows.