Create, reuse, and clean up git worktree lanes for development tasks.
npx skills add https://github.com/hack-ink/codexlab --skill worktrees-hack-ink
Please help me install this Agent Skill. Skill: worktrees Source: https://github.com/hack-ink/codexlab/tree/main/.codex/skills/worktrees Command: npx skills add https://github.com/hack-ink/codexlab --skill worktrees-hack-ink
This skill coordinates and governs the use of git worktree lanes to separate development tasks, enabling safe isolation, predictable lane lifecycle, and clear cleanup without impacting main branches.
Create or reuse a dedicated worktree lane (e.g., .worktrees/<lane>) and begin work in that lane using the repository's bootstrap guidance.
High-intent search queries and answers about installing and using this skill.
To manage git worktrees for isolated development tasks, you can create or reuse a dedicated .worktrees/<lane> directory for each task. This ensures changes are separated across lanes and provides clean diffs without impacting main branches.
A worktree lane is a predictable, isolated .worktrees/<lane> directory used to separate non-read-only development tasks. You need it when starting, resuming, or cleaning up work across multiple branches to ensure safe isolation and predictable lane lifecycle.
To clean up git worktrees after finishing a development task, the workflow handles automatic closeout of lanes and removes lane state when work is complete. This ensures clean reconciliation without leaving residual branch state.
Yes, git worktree lane management works without affecting your main branch by keeping changes separated across lanes. It enforces isolation rules and ensures worktrees are ignored by default to maintain clear cleanup and safe development.
The best way to switch between multiple git branches without stashing is using a worktree lane model. It provisions a dedicated .worktrees/<lane> directory for each task, keeping isolated development contexts separate and ensuring clean diffs.
alexanderopCreate isolated git worktrees for feature branches with safety checks.
yash-gargResolve in-progress git merge and rebase conflicts by analyzing changes and completing integration workflows.
xlelibertyVerify tests and merge or create pull requests for development branches.
LarryHsiaoSwitch Git branches safely by stashing or temporarily committing uncommitted changes.
