cleanup-worktree
Skill0 starsChanged 3 months agoMITView on GitHub
Remove a git worktree after a feature branch has been merged.
- Commits and pushes
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buildSkill
- db-querySkill
- db-searchSkill
- dd-errorsSkill
- devops-wiki-updateSkill
- devops-workitem-createSkill
- devops-workitem-readSkill
- devops-workitem-updateSkill
- finalize-taskSkill
- find-codeSkill
- merge-mainSkill
- panel-review-fixSkill
- panel-reviewSkill
- prSkill
- rebase-mainSkill
- starttaskSkill
- testSkill
- ask-codexSkill
- ask-geminiSkill
- councilSkill
- dailySkill
- find-sessionSkill
- merged-prsSkill
- mm-notifySkill
- optimize-promptSkill
- qSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Ask before deleting remote branch
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cleanup Worktree
Work item ID: $ARGUMENTS
Your task
- Verify the worktree exists:
git worktree list | grep "$ARGUMENTS" - Check if the feature branch was merged (from the main repo):
cd /c/work/Payments && git fetch origin && git branch -r --merged origin/main | grep "$ARGUMENTS" - If merged, remove the worktree:
git worktree remove /c/work/$ARGUMENTS_* - Prune stale references:
git worktree prune - Optionally delete the remote branch (ask user first):
git push origin --delete feature/$ARGUMENTS_*
Output
Report:
- Whether the branch was merged
- Worktree removal status
- Ask before deleting remote branch
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.