plugins-copilot/git-worktree/skills/worktree-remove/SKILL.md
Remove a linked git worktree when parallel work is complete. Trigger when the user says "remove worktree", "delete worktree X", "clean up the worktree", "/worktree-remove", or finishes a feature and wants to tear down the parallel checkout. Optional `--delete-branch` also drops the branch; `--force` removes worktrees with uncommitted changes.
npx skillsauth add st0nefish/claude-toolkit worktree-removeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Remove a linked git worktree. Optionally delete its branch. Use direct
git worktree commands rather than plugin helper-script paths; the
plugin-root environment variable is not guaranteed to exist inside Bash
tool invocations.
Identify the target. The user can pass:
feature-auth) — resolved against the entries in
git worktree list --porcelain (match the leaf directory under
${WORKTREE_BASE_DIR:-<repo-root>/.github/worktrees})Check for uncommitted changes by inspecting the matching record from
git worktree list --porcelain. If the worktree is dirty and the user
did not request --force, refuse and explain.
Remove the worktree with git worktree remove <path>. Pass --force
when the user explicitly requested it for a dirty worktree.
If the user passed --delete-branch, run git branch -d <branch> after
removal. Use git branch -D <branch> only when the user explicitly
confirms a force-delete (branch unmerged).
Run git worktree prune to clean up stale administrative state.
Confirm removal to the user.
--delete-branch uses git branch -d (safe delete — fails if unmerged).
Tell the user if the branch wasn't deleted and how to force-delete.git worktree prune runs automatically after removal.development
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Interact with GitHub and Gitea issue trackers and CI systems. List and show issues, file bugs, comment on issues or PRs, list and show pull requests, and fetch CI run logs — all from any repo context without leaving the session.