Session Report
Updated
Analyzes your Claude Code session and generates a structured report of what changed, what decisions were made, and what's left to do.
/plugin install session-report Anthropic official marketplace skill
What it does
After a long coding session it’s hard to remember exactly what happened: which files changed, which decisions were made, what’s half-done. Session Report inspects the session and produces a structured summary covering the work completed, files touched, decisions recorded, and any follow-ups.
What you get
- Files changed — concise list with a one-line reason per file
- Decisions — notable choices (e.g. “switched from lodash to native ES”)
- Follow-ups — anything left open at the end of the session
- TL;DR — short narrative suitable for a PR description or standup update
Use cases
- At end of day, generate a session report as your daily work log.
- Before writing a PR, use the report to make sure you captured every change.
- Share a summary based on the report when handing off work to a teammate.
Frequently Asked Questions
What is Session Report?
An Anthropic official marketplace skill that analyzes a Claude Code session and produces a structured report of changed files, what was done, and the decisions made.
Where does it run?
Claude Code.
How do I install it?
In Claude Code, run `/plugin install session-report`.
How do I invoke it?
Ask in natural language at session end (e.g. "generate a session report") and the structured report is produced immediately.
When is it most useful?
End-of-day work logs, pre-PR change review, and sharing what you did with teammates as a concise summary.