session-report

Analyze conversation edits, writes, and commands to generate a Russian stakeholder report.

25|5|Updated Mar 25, 2026

Search Tags:#analysis #feature #session #product #report #summarize #stakeholders

Ready to run

npx skills add https://github.com/Hedgehogues/awesome-claude --skill session-report-hedgehogues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-report
Source: https://github.com/Hedgehogues/awesome-claude/tree/main/skills/session-report
Command: npx skills add https://github.com/Hedgehogues/awesome-claude --skill session-report-hedgehogues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Generates a product-focused session report from the current conversation by analyzing actions such as edits, writes, and shell commands in context, and presents a concise, stakeholder-friendly summary in Russian without exposing git activity.

Core Features & Use Cases

Analyze conversation history to identify files changed, files created, and commands executed.
Group changes into product themes and features, including frontend, backend, and migrations where relevant.
Produce a clear, Russian-language stakeholder summary suitable for reviews and decision making.

Quick Start

Generate a product-focused session report from the current conversation.

Frequently Asked Questions about session-report

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

FAQPage Schema

How do I summarize a coding session into a product report for stakeholders?▼

To summarize a coding session into a product report for stakeholders, this Skill analyzes conversation history including edits, writes, and shell commands, grouping changes into product themes and affected areas for a structured summary.

What is the best way to generate a feature-based summary from recent development changes?▼

Generating a feature-based summary from development changes is best handled by analyzing shell invocations and file edits to identify product impacts, which are then grouped into themes like frontend, backend, or migrations for a structured output.

Does the session report include git activity and commit history?▼

No, the session report does not include git activity. It focuses strictly on analyzing actions within the current conversation, such as file edits, writes, and shell commands, to summarize product-impact changes.

Can I use this session report tool if my project context involves database migrations?▼

Yes, you can use this session report tool for project contexts involving database migrations. It identifies product changes and explicitly groups them into feature-based themes, including migrations and follow-ups where relevant for stakeholder review.

Do I need jq installed to generate a stakeholder-friendly product summary?▼

Yes, you need jq installed because it is a required dependency. The tool uses this component to process and analyze conversation data to produce the final structured report for stakeholders.

Why is the generated session report output in Russian rather than English?▼

The generated session report output is in Russian because the Skill is specifically designed to produce a clear, Russian-language stakeholder summary suitable for product reviews and decision making.