handoff

Generate a structured handoff document capturing branch, commits, open PRs, failing tests, and next steps.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill handoff-sburl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/handoff
Command: npx skills add https://github.com/sburl/CrossCheck --skill handoff-sburl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoff generation reduces cognitive load and prevents context loss by producing a structured document that captures the current session state, including branch, recent commits, open PRs, test status, and next steps.

Core Features & Use Cases

  • Capture current state: branch, commits, open PRs, and failing tests.
  • Generate a reusable do-work/handoff.md document with a consistent structure for seamless transitions.
  • Support targeted handoffs: tailor guidance for Codex, Gemini, or other agents.

Quick Start

Ask your agent to generate a session handoff from the current repository state.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a session handoff document for agent-to-agent context continuity?

Generate a session handoff by capturing the current branch, commits, open PRs, failing tests, and next steps into a standardized do-work/handoff.md template for seamless agent-to-agent context continuity.

What is the best way to preserve session state when switching between AI agents?

The best way to preserve session state when switching AI agents is to produce a structured handoff document that captures current repository state and decisions, preventing context loss and reducing cognitive load.

Can I tailor session handoff guidance for specific agents like Codex or Gemini?

Yes, you can tailor session handoff guidance for specific agents like Codex or Gemini by generating targeted handoff documents that capture branch, commits, open PRs, test status, and next steps for seamless transitions.

Do I need a SKILL.md file to output a standardized handoff template?

Yes, you need a SKILL.md frontmatter with a name and description to output a standardized do-work/handoff.md template that captures your current session state and next steps.

What repository information is captured to prevent context loss during session switches?

To prevent context loss during session switches, the handoff captures the repository's current branch, recent commits, open PRs, failing tests, and next steps in a structured document for seamless continuity.