worktree-handoff

Create git worktrees with CONTEXT.md and copied environment configs.

127|8|Updated Apr 6, 2026

Search Tags:#git #workflow #context #worktree #handoff #task-management

Ready to run

npx skills add https://github.com/hanamizuki/solopreneur --skill worktree-handoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-handoff
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/solopreneur/skills/worktree-handoff
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill worktree-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create an isolated workspace for a new or in-progress task, and write the complete task context into the new worktree so the next session doesn't need to start from scratch.

Core Features & Use Cases

Create a new worktree under .worktrees/ with a branch name derived from task type (bug fix, feature, refactor, research).
Copy relevant gitignored environment/config files from the main repository into the worktree.
Generate docs/CONTEXT.md in the new worktree containing problem background, root cause, items to fix, key files, and current progress.
Provide an output-ready command sequence for the user to switch to the new worktree and proceed.

Quick Start

Create a new worktree for the current task and generate a complete CONTEXT.md in the worktree.

Frequently Asked Questions about worktree-handoff

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

FAQPage Schema

How do I preserve git task context for a worktree handoff to a new session?▼

To preserve git task context, create a worktree under .worktrees/ and generate a docs/CONTEXT.md file capturing the problem background, root cause, and current progress so the next session resumes seamlessly.

Can I copy gitignored environment configs when creating a new git worktree?▼

Yes, gitignored environment config files can be selectively copied from the main repository into the new worktree during creation, ensuring the isolated workspace has the necessary local settings to run immediately.

How do I separate bug fix or feature work from the main branch using git worktrees?▼

You can separate work by creating a new git worktree with a branch name derived from the task type, such as bug fix, feature, refactor, or research, keeping the main branch clean and decoupled.

What is the best way to document task history and file maps for in-progress git work?▼

The best way to document task history is generating a CONTEXT.md file inside the worktree that details the root cause, items to fix, key files, and current progress, preserving the full task history for later sessions.

Does git worktree naming need to follow a specific format for task management workflows?▼

Git worktree naming enforces deterministic conventions based on the task type, ensuring consistent branch identification across bug fixes, new features, refactors, and research tasks for reliable task management.

How do I switch to a new worktree and continue a task after generating context?▼

After generating the worktree and CONTEXT.md, the process outputs a ready-to-use command sequence that you run to switch directories into the new workspace and proceed with the task immediately.