write-handoff

Generate a phase-based GitHub issue handoff comment with validation steps.

4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/greenheadHQ/nixos-config --skill write-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-handoff
Source: https://github.com/greenheadHQ/nixos-config/tree/main/modules/shared/programs/claude/files/skills/write-handoff
Command: npx skills add https://github.com/greenheadHQ/nixos-config --skill write-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing consistent, phase-based migration handoff comments on GitHub issues is time-consuming and error-prone without a repeatable template.

Core Features & Use Cases

  • Generate a structured, multi-phase handoff plan tailored to the given issue.
  • Provide BEFORE/AFTER content for code changes, validation steps, and commit templates.
  • Attach a ready-to-post GitHub comment that can be pasted into the issue or PR discussion.

Quick Start

Invoke this skill with an issue number or URL to generate a ready-to-post handoff comment.

Frequently Asked Questions about write-handoff

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

FAQPage Schema
How do I automate drafting a GitHub issue handoff comment for LLM migrations?

Automating a GitHub issue handoff comment involves generating a structured, multi-phase plan with validation steps and commit templates. This skill parses the given issue to produce a ready-to-post comment for migration handoffs.

What is phase-based issue handoff planning in software engineering?

Phase-based issue handoff planning is structuring a migration task into sequential steps with BEFORE/AFTER content and validation checks. This approach ensures consistent, repeatable handoff guidance for GitHub issues.

How do I generate a ready-to-post GitHub comment for a migration handoff?

To generate a GitHub comment, invoke this skill with an issue number or URL. It applies a multi-phase workflow and references template to output a structured comment with code changes and validation steps.

Does this handoff skill require specific dependencies to parse GitHub issues?

No specific dependencies are required to parse GitHub issues for handoff planning. The skill needs a frontmatter-defined name and description, alongside a references template to function correctly.

What should I include in an LLM-driven migration handoff guide?

An LLM-driven migration handoff guide should include multi-phase planning, BEFORE/AFTER content for code changes, validation steps, and a commit template. Optional DA feedback guidance can also be attached.