worktree

Create isolated JJ workspaces with jj workspace add and integrate via jj squash.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ormastes/simple --skill worktree-ormastes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/ormastes/simple/tree/main/doc/00_llm_process/skill_command/skills/claude/lib/worktree
Command: npx skills add https://github.com/ormastes/simple --skill worktree-ormastes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Worktree Skill provides isolated JJ workspace environments to separate working copies and support parallel development without impacting the primary workspace.

Core Features & Use Cases

  • Create isolated workspaces using jj workspace add to spin up parallel development tracks.
  • Work within a separate workspace, switch contexts, and commit changes with jj commit.
  • Integrate changes back into the main codebase via jj squash --from <change_id> and cleanup when done.
  • Enforce guidelines to not use EnterWorktree/ExitWorktree and ensure proper lifecycle management.

Quick Start

Create a new isolated JJ workspace, work in it, commit changes, and integrate back to the main branch.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I create isolated JJ workspaces for parallel development tasks?

Isolated JJ workspaces are created using the jj workspace add command to spin up parallel development tracks. This separates your working copies, allowing you to develop multiple features simultaneously without impacting the primary workspace or interfering with other ongoing tasks.

What is the best way to integrate changes from a separate JJ workspace back to the main branch?

The best way to integrate changes from a separate JJ workspace back to the main branch is by using jj squash --from <change_id>. This command merges your committed changes from the isolated workspace into the main codebase for final consolidation.

Can I use this for managing multiple parallel features without affecting my main working copy?

Yes, this approach is specifically designed for multi-task development scenarios where multiple features are developed in parallel. It provides dedicated workspaces for each task, ensuring changes in one isolated environment do not affect the main working copy.

How do I record changes within an isolated JJ workspace?

To record changes within an isolated JJ workspace, use the jj commit command. This saves your modifications within the separate workspace context, keeping the tracked changes distinct from the main working copy until you are ready to integrate them.

Why should I avoid using EnterWorktree and ExitWorktree when managing isolated workspaces?

You should avoid using EnterWorktree and ExitWorktree because this workflow enforces proper lifecycle management using native JJ commands instead. Relying on jj workspace add and jj squash ensures safer parallelism and cleaner integration back into the main codebase.