claude-context: Skill for Claude Code

PR Cleanup

Post-merge housekeeping. Run this after a PR has been merged to main — before /wrap. It is safe to run even if no PR was merged this session; it will just report that nothing needed cleaning.

Run the entire flow autonomously. The user invoked /pr-cleanup once — that is the permission to clean up merged state. Do NOT ask for permission between steps.

---

When to run

• After a PR merged to main this session
• When git worktree list shows stale worktrees
• Anytime branches marked [gone] are piling up

If this session had no PR activity and no stale branches, report that briefly and exit. Do not run the full flow unnecessarily.

---

The Flow

Step 1 — Snapshot current state (parallel)

git fetch --prune --all
git branch -vv                          # shows [gone] branches
git worktree list
git log --oneline @{u}..HEAD 2>/dev/null   # commits ahead of origin
git log --oneline HEAD..@{u} 2>/dev/null   # commits behind origin
gh pr list --author "@me" --state merged \
  --search "merged:>=$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d 'yesterday' +%Y-%m-%d)" \
  --json number,title,headRefName,mergedAt 2>/dev/null

Hold all results in working memory. Do not display yet.

Step 2 — Remove merged worktrees

For each entry in git worktree list (excluding the main worktree):

1. Check if the worktree's branch appears in git branch -vv output as [gone] — meaning the remote branch has been deleted (i.e., merged and cleaned up by GitHub).
2. If [gone]:
   • Check for uncommitted changes: git -C <worktree-path> status --short
   • If clean → remove the worktree: git worktree remove <worktree-path> --force
   • If dirty → do NOT remove. Add to warnings: "Worktree <path> has uncommitted changes — left intact. Review manually."
3. If NOT [gone] (branch still exists on remote) → leave it alone, no warning needed unless it's been open for >7 days (then add a soft note).

Step 3 — Update main WITHOUT switching branches