session-end

Name: session-end
Availability: InStock
Author: Bryce

Generate an evidence-grounded session record with decisions, claims, and artifacts.

Updated Jun 16, 2026

Search Tags:#workflow #resume #artifacts #evidence #handoff #session-end

Ready to run

npx skills add https://github.com/BryceEWatson/claude-global-skills --skill session-end-bryceewatson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/BryceEWatson/claude-global-skills/tree/main/session-end
Command: npx skills add https://github.com/BryceEWatson/claude-global-skills --skill session-end-bryceewatson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close out a Claude Code session by producing an evidence-grounded record of decisions, claims, and artifacts, ensuring zero memory gaps when a session ends or is handed off.

Core Features & Use Cases

Evidence synthesis: reconstructs the session from artifacts such as git status, git diff, and commit history to produce a traceable record.
Handoff and resumable state: captures the exact in-flight state and emits a ready-to-paste continuation prompt for the next session.
Artifact tracking: enumerates created/modified files and their rationales to support auditability.

Quick Start

Invoke with /session-end in Claude Code to close the current session and generate a handoff when work is in progress.

Frequently Asked Questions about session-end

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

FAQPage Schema

How do I create a resumable handoff document for an in-progress coding session?▼

To create a resumable handoff document, invoke the session close workflow to synthesize git status, git diff, and commit history into an evidence-grounded record with a ready-to-paste continuation prompt for the next session.

What is the best way to track artifacts and decisions when ending a Claude Code session?▼

The best way to track artifacts and decisions when ending a session is to reconstruct the workflow from git commit history and file modifications, producing a structured, verifiable summary that enumerates created files and their rationales.

Does the session handoff workflow work without external dependencies?▼

Yes, the session handoff workflow operates with zero external dependencies, relying entirely on native git artifacts like git status, git diff, and commit history to reconstruct decisions and produce a traceable record.

Why do I lose context when handing off my code to a new session?▼

You lose context when handing off code because standard sessions lack a durable, evidence-grounded record of in-flight decisions and artifacts, a gap solved by synthesizing git history into a structured, verifiable summary document.

How do I generate an audit trail for modified files when closing a development session?▼

To generate an audit trail for modified files when closing a session, use a workflow that enumerates created and modified files alongside their rationales, supporting auditability by grounding claims in git diff evidence.