worker-cleanup
Remove completed or abandoned worker worktrees and their branches. Use to clean up after workers finish their tasks.
What this skill does
# Worker Cleanup Skill
Remove completed or abandoned worker worktrees.
## Usage
```
/worker-cleanup [worktree-path-or-branch]
/worker-cleanup --all-merged
/worker-cleanup --all
```
## Examples
```
/worker-cleanup ../artemis-issue-42
/worker-cleanup feat/issue-42-retry
/worker-cleanup --all-merged
```
## Instructions
### Single Worktree Cleanup
When given a specific worktree or branch:
1. **Check for uncommitted changes**
```bash
cd <worktree> && git status --porcelain
```
If dirty, warn user and ask for confirmation.
2. **Check if branch was merged**
```bash
git branch --merged main | grep <branch>
```
If not merged, warn user about unmerged commits.
3. **Remove worktree**
```bash
git worktree remove <worktree-path>
```
4. **Delete branch if merged**
```bash
git branch -d <branch> # Safe delete (fails if unmerged)
```
### Cleanup All Merged (`--all-merged`)
Find and remove all worktrees whose branches are merged to main:
```bash
# Get merged branches
MERGED=$(git branch --merged main | grep -v main)
# For each, remove worktree and branch
for branch in $MERGED; do
worktree=$(git worktree list | grep "$branch" | awk '{print $1}')
if [ -n "$worktree" ]; then
git worktree remove "$worktree"
git branch -d "$branch"
fi
done
```
### Cleanup All (`--all`)
**DANGEROUS** - Removes all non-main worktrees:
1. List all worktrees
2. Show uncommitted/unmerged status for each
3. Require explicit confirmation
4. Remove each worktree and optionally delete branches
### Output
Show cleanup summary:
```
Cleaned up 3 worktrees:
- ../artemis-issue-42 (feat/issue-42-retry) - merged, deleted
- ../artemis-feat-logging (feat/add-logging) - merged, deleted
- ../artemis-old-experiment (test/old) - unmerged, branch kept
Remaining worktrees: 1
- ../artemis-wip (feat/work-in-progress) - has uncommitted changes
```
## Safety
- Never remove main worktree
- Warn before removing worktrees with uncommitted changes
- Keep unmerged branches by default (use `-D` flag to force)
- Always show what will be deleted before confirming
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.