session-summary

Summarizes Claude Code sessions and feeds lessons back into skills and AGENTS.md files.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/lldwb/lldwb-claude-skills --skill session-summary-lldwb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-summary
Source: https://github.com/lldwb/lldwb-claude-skills/tree/main/skills/session-summary
Command: npx skills add https://github.com/lldwb/lldwb-claude-skills --skill session-summary-lldwb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? After a long Claude Code session, valuable lessons and skill improvement ideas are easily lost. This Skill closes out a session by extracting what actually happened, identifying which skills have gaps, and routing lessons to the right place before they are forgotten. ## Core Features & Use Cases - Session Forensics: Extracts user messages, assistant replies, timelines, or compact transcripts from multi-megabyte Claude Code session JSONL files via a Python script, writing results to disk instead of loading everything into context. - Skill Iteration Assessment: Maps each discovered problem or lesson to a specific skill defect, missing rule, or capability gap, then produces a prioritized optimization list with value, cost, and recommendation for user approval. - Cross-Repository Lesson Reflux: When the session operated on another project repository, writes empirically verified lessons into that repository's own AGENTS.md following its commit conventions. - Use Case: After finishing a debugging session in a client project, ask for a session summary to get a traceable recap, an update to that project's AGENTS.md with newly proven pitfalls, and a confirmed list of improvements to apply to the skills repository. ## Quick Start Ask the assistant to summarize this session and evaluate whether any skills should be improved based on what happened.

Frequently Asked Questions about session-summary

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

FAQPage Schema
How do I summarize a Claude Code session without reading the whole transcript?

Run the extract-session.py script with a session ID or JSONL path and choose a mode: --user for full user messages, --assistant N for the last N assistant replies, --timeline for an event timeline, or --transcript for a compact full record. Output is written to .tasks/session-extract/ by default.

How to extract user messages from Claude Code session JSONL files?

Use extract-session.py with the --user flag, which prints every user message with timestamps and no truncation by default. The script locates files under ~/.claude/projects/ using the project's escaped path, or accepts a direct .jsonl file path.

Does the session extraction script need external Python packages?

No, extract-session.py uses only the Python 3 standard library. It requires Python 3 and access to Claude Code session record files stored under ~/.claude/projects/.

When should lessons go into AGENTS.md instead of a skill?

Lessons specific to one project's mechanisms, boundaries, or pitfalls belong in that project's own AGENTS.md, committed under that repository's conventions. Generalizable rules that hold across projects belong in the skills repository. The deciding test is whether the lesson still holds in a different project.

What are the limitations of session-summary?

It only evaluates and proposes improvements; actual implementation is delegated to feature-dev, bug-fix, or refactor skills. It does not review commit quality (use commit-review) or rewrite history (use git-history-rewrite), and it requires existing Claude Code session record files to perform forensics.