gsd-session-report

Generate a structured SESSION_REPORT.md with session outcomes and token usage estimates.

8|Updated Apr 9, 2026

Search Tags:#automation #workflow #documentation #session #claude-code #report #token-usage

Ready to run

npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-session-report-d0nmega

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-session-report
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-session-report
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-session-report-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a structured SESSION_REPORT.md document that captures session outcomes, work performed, and token usage estimates for post-session review.

Core Features & Use Cases

Automated generation of a SESSION_REPORT.md capturing outcomes, work performed, and token usage estimates.
Generates a shareable artifact suitable for post-session reviews and audits.
Use Case: After a Claude Code session, generate a standardized report summarizing tasks completed, decisions made, and resource usage.

Quick Start

Invoke the session-report workflow to generate and save a session report for the current Claude session.

Frequently Asked Questions about gsd-session-report

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

FAQPage Schema

How do I generate a session report for Claude Code workflows?▼

To generate a session report for Claude Code workflows, invoke the session-report workflow to automatically load a predefined template, capture session outcomes, and output the structured report to a known directory.

Can I estimate token usage for post-session reviews automatically?▼

You can estimate token usage for post-session reviews automatically by triggering the session report generation, which captures work performed, session outcomes, and token usage estimates into a standardized artifact.

What is the best way to document debugging sprints and session outcomes?▼

The best way to document debugging sprints and session outcomes is to generate a structured SESSION_REPORT.md file that summarizes tasks completed, decisions made, and resource usage into a shareable artifact.

Does the session report workflow require any dependencies or components?▼

The session report workflow requires no external dependencies or components, allowing you to execute the predefined template workflow and output the report directly without additional environment setup.

When do I need to create a standardized session report file?▼

You need to create a standardized session report file after completing a Claude Code session or debugging sprint when you require a shareable artifact for post-session reviews, audits, or team documentation.