Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
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.
npx claudepluginhub mgdickinson/worktree-fleetHow 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:
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
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.