deferred/remove-worktree
home/dot_agents/skills/remove-worktree/SKILL.md
Remove git worktrees using the Worktrunk CLI `wt`. Use this skill when the user asks to "remove a worktree", "delete a worktree", "clean up a worktree", "remove branch worktree", or wants to get rid of a parallel development environment. Also trigger when the user mentions removing or deleting worktrees in any form.
tools
Updated Apr 29, 2026
$ install --global
skillsauthnpx skillsauth add deferred/dotfiles remove-worktreeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 4:34 AM214.2s1 file scanned
SKILL.md
- name:
- remove-worktree
- description:
- >
Remove Worktree
Use the Worktrunk CLI wt to remove git worktrees.
Steps
-
Identify the target worktree from the user's request.
-
Confirm which worktree to remove only if the target is unclear. If it is obvious from context, such as "remove the feature-x worktree", proceed without asking.
-
Run the removal:
wt remove <branch> --foregroundOmit
<branch>to remove the current worktree. -
Handle failures. If the command fails, suggest the appropriate flag:
- Untracked files (build artifacts, IDE config): add
--force(-f) - Unmerged branch commits: add
--force-delete(-D) - Both issues: add both flags
Always explain what the flag does before running with it, so the user can make an informed call.
- Untracked files (build artifacts, IDE config): add
-
Verify the command succeeded and report the result to the user.
Useful flags
| Flag | When to use |
| --- | --- |
| --force / -f | Worktree has untracked files (will not affect the branch) |
| --force-delete / -D | Branch has unmerged commits |
| --no-delete-branch | Keep the branch after removing the worktree |
| --foreground | Wait for completion (recommended when running as an agent) |
By default, wt remove also deletes the branch if it is already merged. That is usually what you want.
Use --no-delete-branch if the user wants to keep the branch.
Related Skills
deferred/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated Apr 29, 2026
deferred/caveman
testing
VerifiedTrustedCommunity
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
SKILL.mdUpdated Apr 29, 2026
deferred/markdown-style-guide
development
VerifiedTrustedCommunity
Write and revise Markdown so it is clean, scannable, and consistent. Use this skill whenever you are about to produce Markdown of any kind, including READMEs, docs, guides, notes, reports, issue bodies, pull request text, or comments, even if the user did not explicitly ask for Markdown formatting.
SKILL.mdUpdated Apr 25, 2026
deferred/git-commit
research
VerifiedTrustedCommunity
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
SKILL.mdUpdated Apr 24, 2026