agentleFS
Sign inStart free
bordenetbordenet/superpowers-plus/skills/engineering/session-handoff/skill.md

session-handoff

Skill8 starsChanged 6 months agoMITView on GitHub

Cold-start advisory: surfaces commits on remote-tracking refs that landed in the last 24 hours and are NOT yet on any local branch. Catches the incident-2026-1507 pattern where a sibling machine pushed work between sessions and the next session edited blind. Read-only; never blocks.

139 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, research-fleet and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • SethGammonSkill

    research-fleet

    Parallel research using Fleet wave mechanics. Spawns multiple scout agents, each investigating a different angle of the same question. Findings are compressed between waves. Produces a unified research brief from multiple independent perspectives.

    Also in 3 projects that use this

  • vicoa-aiSkill

    live-preview

    Start a local app in the current user project, expose it through a tunnel, and return preview details in structured Markdown. Use when the user asks for a preview URL, public URL, shareable localhost, mobile/web preview, or tunnel setup.

    Also in 4 projects that use this

  • botlearn-aiSkill

    doc-gen

    Also in 4 projects that use this

  • flyingobsidianSkill

    terminology

    Read a codebase, find terminology, create/update definitions into a markdown document.

    Also in 3 projects that use this

  • Dizzy-TenSkill

    bug-diagnosis

    Diagnose bugs and product issues without modifying code. Use when the user explicitly invokes $bug-diagnosis or asks for diagnosis, root-cause analysis, issue classification, or fix strategy for code bugs, failing tests, configuration/dependency problems, deployment issues, performance regressions, data anomalies, or frontend/user-experience problems described through screenshots, annotations, logs, errors, or natural-language reports. Prioritize analysis and recommendations only; do not edit files.

    Also in 3 projects that use this

  • +1 more from SethGammon

The file

Create a free account to mount
Files
skill.md

Session Handoff

Wrong skill? Resuming an explicit prior context -> branch-sync-gate (fetches + checks behind/diverged). Per-branch budget doc -> hotfix-charter. Per-commit LOC ceiling -> pre-push-loc-gate. Cumulative branch vs ticket estimate -> scope-tripwire.

A first-touch advisory that asks: what landed in this repo since I last looked? Lists commits on remote-tracking refs from the last 24 hours that are NOT yet reachable from any local branch -- the actionable handoff set. Run it BEFORE editing on a cold start.

When this fires (vs. branch-sync-gate)

Verb / phraseSkillWhy
"let me check this repo" / "starting work on..." / "what's new in..."session-handoffCold start; engineer needs to see what landed
"continuing work on..." / "resuming where I left off..."branch-sync-gateExplicit resume; fetch + behind/diverged check
/sp-session-handoff (explicit)session-handoffManual invocation
/sp-sync (explicit)branch-sync-gateManual invocation

Both should run when both verbs are present. Session-handoff runs first (order: -1), reports the sibling-activity summary, then branch-sync-gate handles the fetch + alignment workflow.

Quick start

# Manually, from the repo root
tools/session-handoff-check.sh

# With assurance line when no activity found
tools/session-handoff-check.sh --verbose

# Wider window (default: "24 hours ago")
SESSION_HANDOFF_WINDOW="7 days ago" tools/session-handoff-check.sh

# Skip the git fetch (offline or hostile network)
SESSION_HANDOFF_NO_FETCH=1 tools/session-handoff-check.sh

What it shows

Output (stderr; nothing on stdout):

session-handoff: sibling activity detected (window: 24 hours ago)
  (Read these commits before editing -- they may overlap your planned work.)

  origin/fix/incident-2026-1507-intro-protection
    2026-06-09T14:32  user@example.com  fix: greeting registration race
    2026-06-09T15:14  user@example.com  test: add ceiling-hit case

  origin/main
    2026-06-10T11:22  user@example.com  Merge commit message

  Tip: `git log <ref> --since="24 hours ago"` for full detail.

Silent when no commits match (unless --verbose).

Configuration

Env varDefaultPurpose
SESSION_HANDOFF_WINDOW24 hours agoAny git log --since= expression
SESSION_HANDOFF_VERBOSE01: print assurance line when no activity
SESSION_HANDOFF_NO_FETCH01: skip git fetch (uses stale local refs)
SESSION_HANDOFF_FETCH_TIMEOUT10Wall-clock budget for fetch (seconds)

Exit codes

ExitMeaning
0Activity surfaced; OR no activity; OR fetch failed (advisory only -- never blocks)
2Not in a git repo, OR invalid env var, OR git log error

Composition with peer skills

session-handoff is the COLD-START half of the session-orientation pair:

+-- session-start group --------------------+
|                                            |
|  [order: -1]  session-handoff              |  <-- "what landed since I left?"
|       |                                    |
|       v   produces: sibling-activity       |
|                                            |
|  [order:  0]  branch-sync-gate             |  <-- "now fetch + reconcile"
|                                            |
+--------------------------------------------+

Both skills running back-to-back is intended ergonomics. The incident-2026-1507 pattern would have been caught by this skill firing on cold-start verbs.

Why this exists

The 2026-06-10 incident-2026-1507 involved two machines doing parallel work on the same hotfix branch. Branch-sync-gate did not fire because the engineer never said "continuing" or "resuming" -- it was a cold start with edit verbs ("let me look at..."). The sibling commits sat invisible on the feature branch while the engineer started a second parallel implementation. Hours of fork-merge confusion followed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free