handoff-pull

handoff-pull

Pick up work from a handoff/<topic> branch produced by the handoff-push skill.

Pre-flight

• You must be inside a git repo with an origin remote. If not, stop and tell the user.
• The working tree should be clean. If there's uncommitted work, stop and ask the user what to do with it — do not overwrite their state.

Steps

1. Fetch:

   git fetch --all --prune
   

2. Pick the branch. If the user named a specific handoff/<topic>, use it. Otherwise list candidates sorted by recency:

   git for-each-ref --sort=-committerdate --format='%(refname:short)  %(committerdate:relative)' refs/remotes/origin/handoff/
   

   Present the list (max ~10 entries), then ask which to pick up.

3. Checkout (creates a local tracking branch if needed):

   git checkout handoff/<topic>
   

4. Read .handoff/notes.md from the checked-out branch. If the file is missing, the branch wasn't produced by the handoff-push skill — tell the user and stop.

5. Brief the user. In 2 short paragraphs:

   • Current state — pulled directly from the notes' "Current status" section, condensed.
   • Proposed next action — pulled from the notes' first "Next steps" item. Quote it verbatim; don't invent your own.

   Then ask the user to confirm before doing anything beyond reading.

Invariants

• Do not rebase, merge, or squash the handoff branch into anything.
• Do not delete the handoff branch automatically. Wait for the user to say "done with this handoff" and even then just suggest the cleanup commands — let them run them.
• If the handoff branch has diverged from the parent feature branch, surface that fact to the user (git log --oneline <parent>..handoff/<topic>) but do not auto-reconcile.