Orchestrates Git worktrees as isolated coding lanes for parallel and risky development work.
npx skills add https://github.com/MDSIXONE/opencode-config --skill worktrees-mdsixone
Please help me install this Agent Skill. Skill: worktrees Source: https://github.com/MDSIXONE/opencode-config/tree/main/skills/worktrees Command: npx skills add https://github.com/MDSIXONE/opencode-config --skill worktrees-mdsixone
.slim/worktrees/<slug>/ with consistent branch naming (omos/<slug>) and tracks lane state in a .slim/worktrees.json manifest. - Safety Guardrails: Enforces pre-flight checks, mandatory user confirmation before destructive Git operations, and managed .gitignore/.ignore blocks to keep lane artifacts local. - Four-Phase Workflow: Covers planning and setup, delegated execution inside the lane, diff-based integration with validation, and confirmed cleanup and pruning. - Use Case: When running multiple background agents on separate bugfixes, assign each agent its own worktree lane so their changes never conflict with the main checkout, then review diffs and merge each lane after approval. ## Quick Start Ask the AI to create a new worktree lane for your refactoring task, for example: set up an isolated worktree for the authentication refactor based on the main branch.High-intent search queries and answers about installing and using this skill.
Run git worktree add -b <branch-name> .slim/worktrees/<slug> <base-branch> after confirming the repository state and branch name availability. The skill registers the lane in .slim/worktrees.json and sets up ignore rules so lane artifacts stay local.
Use worktrees for risky refactors, parallel tasks, background agents, or exploratory spikes that would disrupt your active checkout. Avoid them for simple single-file changes, documentation updates, or minor bug fixes where branch switching is sufficient.
Yes, each agent runs with its working directory set to its own worktree path, keeping builds, tests, and edits isolated. Track file or folder ownership per lane to prevent merge conflicts between parallel agents.
First confirm all changes are merged or archived and the worktree has no uncommitted changes, then get user approval and run git worktree remove .slim/worktrees/<slug>. Update .slim/worktrees.json to mark the lane as archived or remove its entry.
Placing worktrees under .slim/worktrees/ inside the repository keeps lanes organized and allows .gitignore and .ignore managed blocks to hide lane artifacts from Git while keeping them readable to tooling. Sibling directories scatter lanes and complicate cleanup.
hack-inkCreate, reuse, and clean up git worktree lanes for development tasks.
TyrizxMerge a topic branch into the base branch and resolve conflicts in the main worktree.
borealBytesSelect minimal OpenClaw tests for local, CI, Docker E2E, and release validation.
linehaul-aiCreate and switch isolated Git worktrees via worktree-manager.sh.