Install
$ agentstack add skill-ondrejdrapalik-worktree-management-skills-wt-clear ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Clear Windows With Finished PRs
wt clear
Display the output. Done.
What it does
One sweep over everything currently rendered on the active surface: herdr workspaces backed by a worktree, or tmux windows in the current session. For each one it reads the git branch, derives owner/repo from the origin remote, and asks gh whether that branch has a finished PR. Matching windows get closed.
--merged-only narrows the check to merged PRs, skipping closed-unmerged ones. That is the conservative filter, and it is what wt-cleanup-loop uses on a timer. A PR closed without merging often means the work is still wanted.
Why this is safe to run casually
Nothing on disk changes. Checkouts stay in ~/_wt, branches stay in git; only the window or workspace closes. Re-open any of them with wt open .
The skips are structural rather than advisory, so you don't need to guard them yourself: the focused window/workspace is never a candidate, main and master are excluded, non-repo paths and branches without a finished PR fall through, and a failing gh/git/herdr call skips that one entry instead of aborting the sweep.
If the user actually wants the checkouts deleted too, that is wt-remove per worktree. Say so rather than guessing.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: OndrejDrapalik
- Source: OndrejDrapalik/worktree-management-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.