What it does

After completing a PR — whether it’s opened, merged, or needs revision — this skill generates a structured handoff prompt capturing the PR state, review feedback, CI results, and pending follow-ups. Paste it into a new conversation to continue without context loss.

When to use it

After opening a PR, before closing the conversation
When CI fails and you need a fresh session to debug
After receiving review feedback that requires changes
When a PR is merged but spawns follow-up tasks

How it works

Add to your CLAUDE.md:

## PR Cycle Handoff

At the end of every PR cycle, produce a self-contained handoff prompt for a
fresh chat window. Include:

- PR number, title, branch, and current status
- Summary of what the PR does (1-3 sentences)
- Review feedback received (if any)
- CI/check status and any failures
- Follow-up items discovered during the PR
- Exact command to check out the branch and continue

Example output

## Handoff — PR #188: feat(org): remove-member capability for admins

**Branch:** `feat/for-115-remove-member` | **Status:** merged to main
**What it does:** Adds admin ability to remove members from an org, with
RLS policy enforcement and cascade cleanup of role assignments.

**Review feedback:** None — approved on first pass.

**CI:** All checks green. E2E tests passed including the new remove-member flow.

**Follow-ups discovered:**

- [ ] Org deletion should cascade member removal (currently orphans)
- [ ] Add rate limiting to the remove-member endpoint
- [ ] 503 error handling for Supabase outages during removal

**To continue:**
git checkout main && git pull

Why it matters

PR cycles often span multiple conversations. Review feedback arrives hours later, CI takes time, and follow-up tasks emerge during implementation. Without a handoff prompt, each new conversation starts from scratch — re-reading the diff, re-discovering the context, and potentially contradicting decisions from the original session. This skill makes PR continuity automatic.