using-git-worktrees

Create isolated Git workspaces with content-addressed rebase for feature development.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/LiGoldragon/Mentci-AI --skill using-git-worktrees-ligoldragon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/LiGoldragon/Mentci-AI/tree/main/.pi/skills/using-git-worktrees
Command: npx skills add https://github.com/LiGoldragon/Mentci-AI --skill using-git-worktrees-ligoldragon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage feature development by isolating code changes, preventing conflicts, and ensuring reproducibility.

Core Features & Use Cases

  • Isolation of Feature Work: Prevents workspace contamination during feature development.
  • Content-Addressed Rebase: Ensures reproducibility of code changes.
  • Use Case: When starting a new feature branch that needs to be isolated from the main development branch.

Quick Start

To create an isolated workspace for your feature, use the command: jj-agent create --workspace <workspace_name>

Frequently Asked Questions about using-git-worktrees

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

FAQPage Schema
How do I create an isolated workspace for feature development?

You can create an isolated workspace for feature development by running `jj-agent create --workspace <workspace_name>`, which sets up an independent Git worktree to prevent workspace contamination.

What is content-addressed rebase in Git worktrees?

Content-addressed rebase in Git worktrees is a mechanism that ensures reproducibility of code changes by cryptographically tracking content during feature development, preventing accidental workspace contamination.

Do I need any specific tools to manage Git worktrees with this approach?

Yes, managing Git worktrees with this approach requires the JJ-agent tool, which orchestrates workspace setup and management to maintain isolation during feature development.

How do I prevent workspace contamination when working on multiple features?

To prevent workspace contamination when working on multiple features, create isolated Git workspaces using the JJ-agent, ensuring each feature branch remains independent and reproducible.

When should I use isolated Git workspaces instead of standard feature branches?

You should use isolated Git workspaces instead of standard feature branches when starting a new feature that requires strict isolation from the main development branch to prevent conflicts and ensure reproducibility.

Does this approach support existing Git repositories?

Yes, this approach supports existing Git repositories by creating isolated worktrees within them using the JJ-agent, allowing feature development without contaminating the primary workspace.