handoff

Generate structured handoff documents from git diff changes.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/phoenicisf/forex-analyzer --skill handoff-phoenicisf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/phoenicisf/forex-analyzer/tree/main/.agents/skills/handoff
Command: npx skills add https://github.com/phoenicisf/forex-analyzer --skill handoff-phoenicisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of a concise handoff document by summarizing git changes, files modified, pending items, and next steps, reducing context-switching overhead and ensuring knowledge transfer.

Core Features & Use Cases

  • Generate a structured handoff from git diff, grouping changes by module/service and listing files touched.
  • Create or update docs/state/{module}/handoff.md and refresh docs/state/overview.md to reflect progress.
  • Support end-of-task, end-of-day, or cross-team handoffs to developers or agents.

Quick Start

Generate a handoff for the current task by summarizing the latest git changes.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I generate a handoff document from git diff for another developer?

To generate a handoff document from git diff, the Skill summarizes code changes by grouping modified files per module, tracking pending items, and creating structured handoff.md entries for seamless developer context transfer.

What is the best way to automate end-of-day code change summaries for team coordination?

Automating end-of-day code change summaries involves parsing git diff to list files by module, recording next steps, and updating overview.md, which reduces context-switching overhead and ensures knowledge transfer.

Can I use this to create a handoff for an AI agent taking over a coding task?

Yes, you can create a handoff for an AI agent. The Skill generates structured state documents with pending items and module-level change summaries, providing the exact context an agent needs to resume development.

How does it track pending items and state across multiple modules?

It tracks pending items and state by creating or updating docs/state/{module}/handoff.md files and refreshing a central docs/state/overview.md file with a per-module handoff entry to reflect current progress.

Do I need any external dependencies to summarize git changes for documentation?

No external dependencies are required to summarize git changes for documentation. The Skill operates independently to parse git diff and generate the required module state files and overview updates.