From worktree-fleet
Use before manually running git pull, git merge main, or git rebase main; safely catch this worktree up to the latest fleet integration target.
How this skill is triggered — by the user, by Claude, or both
Slash command
/worktree-fleet:syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run:
Run:
worktree-fleet sync
If it merges a target, continue normally. If it reports a block, stop and explain the reason to the user. Do not bypass staged-index, active-operation, dirty-overlap, missing-object, or divergent-target blocks.
Do not manually git pull, git merge <integration-branch>, or git rebase <integration-branch> as a substitute for fleet sync. Fleet owns catch-up because it checks sibling worktree state and records blocked reasons.
If the user wants to land the completed current branch back onto the local integration branch, run:
worktree-fleet land
Do not manually switch to the integration branch and merge the feature branch as a substitute.
npx claudepluginhub mgdickinson/worktree-fleetGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.