handoff

Capture branch, uncommitted changes, commits, and key files into a handoff artifact.

6|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill handoff-moberghr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/moberghr/mtk-agent-toolkit/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill handoff-moberghr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handing off lengthy sessions requires preserving context. This skill captures the current session state into a compact recovery artifact so a new session can resume cleanly.

Core Features & Use Cases

  • Capture current branch, uncommitted changes, recent commits, and key files into a handoff artifact.
  • Save to docs/handoffs/YYYY-MM-DD-<slug>.md to enable quick resumption in future sessions.
  • Ensure the artifact is easily readable, non-sensitive, and ready for loading into a new session.

Quick Start

Save the current session snapshot to docs/handoffs using the date and a concise slug.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I save my git session state before hitting the context limit?

Capture your git session state by saving the current branch, uncommitted changes, recent commits, and key files into a compact recovery artifact. This snapshot is saved as a markdown file, enabling the next session to resume quickly before the context limit is reached.

What is a git handoff artifact and how does it preserve workflow context?

A git handoff artifact is a compact markdown file that preserves workflow context by recording the current branch, uncommitted changes, and key files. It allows a teammate or a new session to load the previous state and resume work cleanly without exposing sensitive data.

How do I document uncommitted changes and recent commits for a teammate handoff?

Document uncommitted changes and recent commits by generating a recovery artifact that details the current branch and key files. The file is saved to the docs/handoffs directory using the current date and a concise slug, making it ready for your teammate to load.

Can I use this handoff workflow for long-running git sessions ending prematurely?

Yes, you can use this handoff workflow for long-running git sessions ending prematurely. It captures the session state into a readable, non-sensitive markdown artifact that allows the next session to quickly resume exactly where the previous one left off.

Does the generated handoff artifact expose sensitive data from my working directory?

The generated handoff artifact is designed to be non-sensitive and does not expose sensitive data from your working directory. It captures only the structural session state like branch information, recent commits, and key file references needed for resumption.