session-close

Save session state to issue notes, push work to repositories, and generate handoff instructions.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kirvin/agent-dev-harness --skill session-close-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/kirvin/agent-dev-harness/tree/main/plugins/kf/skills/session-close
Command: npx skills add https://github.com/kirvin/agent-dev-harness --skill session-close-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of closing work sessions in a project by automatically saving session context, pushing work to remote repositories, and generating a handoff block.

Core Features & Use Cases

  • End-of-Session Automation: Automatically saves any in-progress context into issue notes, ensures all work is pushed, and prepares a concise handoff block.
  • Context Persistence: Maintains a record of work-in-progress for easy resumption in the next session.
  • Handoff Simplification: Delivers clear instructions for the next user or session, making the transition smooth.

Quick Start

Run this skill to end the session before exiting Claude Code and create a handoff block for the next team member.

Frequently Asked Questions about session-close

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

FAQPage Schema
How do I automate session closure and generate handoff instructions for my team?

Session closure automation saves in-progress context to issue notes, pushes work to remote repositories, and generates handoff instructions. This ensures seamless team handoff by maintaining a record of work-in-progress for the next session.

Does session-close work with Git and Beads issue tracking systems?

Yes, session-close supports Git and Beads issue tracking systems for repository management and context saving. It directly integrates with these platforms to push work and save state to issue notes without requiring external dependencies.

What's the best way to save project context before exiting Claude Code?

The best way to save project context is running an end-of-session protocol that automatically writes work-in-progress state into issue notes and pushes all work to remote repositories before generating a concise handoff block.

Do I need any external dependencies to automate end-of-session handoff?

No external dependencies are required to automate end-of-session handoff. The skill operates independently to save context, push to repositories, and prepare handoff instructions using only its built-in scripts.

Can I use session-close for context persistence in ongoing project management?

Yes, session-close maintains context persistence by automatically recording work-in-progress state into issue notes. This creates a reliable record that enables easy resumption of project management tasks in the next session.

Why does team handoff fail when context saving is done manually?

Manual context saving often misses in-progress work state or fails to push all code to repositories. Automating session closure standardizes the handoff block generation, ensuring nothing is lost during team transitions.