summarizing-session-end

Generate a session summary file under ~/.claude/session-summaries when a Claude Code session ends.

2|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/qte77/claude-code-plugins --skill summarizing-session-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarizing-session-end
Source: https://github.com/qte77/claude-code-plugins/tree/main/plugins/cc-meta/skills/summarizing-session-end
Command: npx skills add https://github.com/qte77/claude-code-plugins --skill summarizing-session-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a concise session summary at the end of a Claude Code session, capturing decisions, actions, and context for later synthesis.

Core Features & Use Cases

  • Structured notes: generates a consistent session-note file under ~/.claude/session-summaries.
  • Context preservation: preserves key files touched and decisions for post-hoc review.
  • Synthesis-ready output: formats notes for quick ingestion into bigpicture or planning workflows.

Quick Start

Trigger the SessionEnd workflow to generate the summary for the current session.

Frequently Asked Questions about summarizing-session-end

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

FAQPage Schema
How do I automate session summaries for Claude Code?

You can automate session summaries by triggering the SessionEnd workflow, which captures decisions, actions, and context. The summary is generated as a structured note file under ~/.claude/session-summaries for later synthesis.

What is the best way to preserve context after a Claude Code session ends?

The best way to preserve context is generating a structured session summary that records key files touched and decisions made. This creates synthesis-ready output formatted for quick ingestion into planning or review workflows.

Can I use session summaries for research and planning phases in Claude Code?

Yes, session summaries can be generated for research, planning, implementation, and review phases. The output provides concise notes that preserve key context for post-hoc review and future planning workflows.

Do I need a specific file path to save Claude Code session summaries?

Yes, you need a deterministic file path under ~/.claude/session-summaries to save Claude Code session summaries. The skill also requires a defined output template to ensure consistent formatting across all generated notes.

Does generating session notes require any external dependencies or components?

No external dependencies or components are required to generate session notes. The skill operates independently using a defined output template and a deterministic file path under ~/.claude/session-summaries for storage.