session-handoff

Create handoff documents from conversation and git history using markdown templates.

12|3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Fei2-Labs/skill-genie --skill session-handoff-fei2-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/Fei2-Labs/skill-genie/tree/main/skills/session-handoff
Command: npx skills add https://github.com/Fei2-Labs/skill-genie --skill session-handoff-fei2-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the generation of handoff documents, streamlining the process of summarizing and archiving work sessions, especially beneficial in team collaboration or when transferring tasks to another agent or individual.

Core Features & Use Cases

  • Session Summary Creation: Automates the creation of structured handoff documents with details such as goals, files changed, commands run, and next steps.
  • Git State Integration: Incorporates git data to ensure accuracy in changes made during the session.
  • User-friendly Output: Outputs a precise file with key information for a smooth handoff process.

Quick Start

To summarize the current session, use the session-handoff skill.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I automate session summary generation for developer task handover?

Generate session handoff documents by combining conversation history and git state data to capture goals, files changed, and next steps. This automates workflow handover using markdown templates for accurate task transfer.

Does automated documentation for task handover integrate with git history?

Yes, automated documentation for task handover incorporates git state data to ensure accuracy in recording changes made during the session directly within the generated markdown file.

What is the best way to create handoff documents for a multi-activity development session?

The best way to create handoff documents for a multi-activity session is using predefined markdown templates populated with session and git history. This ensures a structured summary capturing all necessary workflow details for the next developer.

Can I use session-handoff for team collaboration without manual summary writing?

Yes, you can use it for team collaboration without manual summary writing. The Skill automates document creation by extracting key information from the session and git state, outputting a precise file for a smooth handover process.

What should be included in automated session summaries for developer handover?

Automated session summaries for developer handover should include session goals, files changed, commands run, and next steps. The Skill structures this information into a markdown file using predefined templates to ensure accurate task transfer.