git-worktree

Enforces Git worktree isolation rules for AI agent file modifications.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/twlines/maslow --skill git-worktree-twlines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/twlines/maslow/tree/main/skills/git-worktree
Command: npx skills add https://github.com/twlines/maslow --skill git-worktree-twlines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces strict rules for AI agents operating within isolated Git worktrees, preventing accidental modifications to the main repository or critical configuration files.

Core Features & Use Cases

  • Worktree Boundary Enforcement: Ensures agents only modify files within their designated worktree.
  • Configuration Protection: Prevents agents from altering core project configuration files like package.json or .git.
  • Use Case: When an AI needs to refactor code in a specific feature branch, this Skill ensures it only touches files within that branch's worktree, safeguarding the main development line.

Quick Start

Use the git-worktree skill to ensure all file modifications are confined to the current worktree.

Frequently Asked Questions about git-worktree

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

FAQPage Schema
How do I isolate Git operations for an AI agent?

To isolate Git operations for an AI agent, you enforce Git worktree boundaries that restrict file modifications to a designated worktree. This prevents agents from altering the main repository or critical configuration files.

What is Git worktree isolation and when do I need it?

Git worktree isolation is the enforcement of boundaries that keep AI agent operations within a specific feature branch worktree. You need it when running agents that refactor code, ensuring they do not touch the main development line.

How can I prevent an AI agent from modifying configuration files?

You prevent an AI agent from modifying configuration files by applying worktree boundary enforcement rules. This specifically safeguards core project files like `package.json` and `.git` from accidental alterations during automated operations.

Does this worktree isolation enforce specific output formats for file operations?

Yes, worktree isolation requires adherence to specific output formats for file operations like create and replace. This ensures all automated modifications remain strictly confined within the established worktree boundary.

What are the limitations of relying on Git worktree isolation for agent execution?

A limitation of Git worktree isolation is that it requires strict adherence to specific output formats for file operations. Agents operating outside these conventions or boundaries may fail to execute modifications properly.