Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From worktree-fleet
Use when starting feature work that needs an isolated Git worktree, before executing implementation plans in a new worktree, or whenever the user says to go in a worktree; fleet-aware replacement for generic git-worktree setup.
npx claudepluginhub mgdickinson/worktree-fleetHow this skill is triggered — by the user, by Claude, or both
Slash command
/worktree-fleet:using-git-worktreesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the fleet-aware Git worktree workflow for this repository.
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.
Use the fleet-aware Git worktree workflow for this repository.
In a worktree-fleet-managed repo, this skill supersedes generic Git worktree guidance. Do not start with raw git worktree add/remove/move/prune/repair or git branch -d/-D.
First inspect the fleet board:
worktree-fleet status --refresh-current
Then:
git worktree list.worktree-fleet status --refresh-current.worktree-fleet sync before editing.worktree-fleet intent declare <path...>.If a fleet hook blocks the raw Git command, follow the hook message, read the fleet board, and retry only the operation that still makes sense.
When the user wants to land completed work back onto the local integration branch, run worktree-fleet land from the completed worktree instead of manually switching branches and merging.