cornerman-resume

/cornerman resume

The full session-restoration skill. where-am-i (#14) gives you the snapshot; resume gives you the reasoning.

Args

Flag	Default	What it does
--issue <N>	auto-detect from branch	Target a specific issue
--branch <name>	current branch	Target a specific branch

What it does that where-am-i doesn't

Question	where-am-i	resume
What state am I in for this issue?	✅	✅
What contract last passed?	✅	✅
What's the suggested next agent?	✅	✅
What changed in main since I started?	—	✅
Does my work overlap with those changes?	—	✅
Should I rebase before continuing?	—	✅

resume invokes where-am-i for the snapshot and then adds the diff-against-main + rebase analysis.

Output sections

1. Where you left off (from where-am-i)
2. What's changed in main since work started — file list + ⚠ overlap warning when those files are also touched by this branch
3. Suggested next step — rebase-first when there's overlap and the branch is behind, otherwise the snapshot's recommendation

How

python3 .claude/plugins/cornerman/scripts/resume/report.py \
  ${ISSUE:+--issue "$ISSUE"} \
  ${BRANCH:+--branch "$BRANCH"}

Pure-python. No new dependencies beyond what where-am-i already needs.

What this is NOT

• /cornerman where-am-i (#14) — that's the cheaper snapshot. If you don't care about main-diff, use where-am-i
• A rebase tool — surfaces the recommendation; the human runs git fetch + git rebase
• A contract-replayer — doesn't re-run the actual transition contracts; reports what where-am-i saw plus the main-diff. Replaying contracts against current state lives in the contract entry point (contracts/check.sh <transition> <N>)

Pairs with

• /cornerman where-am-i (#14) — the snapshot it builds on
• /cornerman retro (#13) — cross-issue, time-windowed view
• Run manifests (#11), telemetry (#5), contracts (#4) — the substrate