session-report

Analyze Git history and state files to generate session summaries.

1|Updated Mar 22, 2026

Search Tags:#code analysis #developer tool #development tracking #project review #session reporting

Ready to run

npx skills add https://github.com/mikemyl/verified-development --skill session-report-mikemyl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-report
Source: https://github.com/mikemyl/verified-development/tree/main/skills/session-report
Command: npx skills add https://github.com/mikemyl/verified-development --skill session-report-mikemyl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you keep a record of your development session, tracking what you've accomplished and planning your next steps.

Core Features & Use Cases

Session Summary: Automatically generate a summary of your work, including features, code changes, verification results, and decisions made.
Session Progress Tracking: Visualize the progress of features through various stages of development.
Quick Report Generation: Present a concise summary directly to aid in decision-making and planning for future sessions.

Quick Start

Run the session-report skill to generate a summary of your current session.

Frequently Asked Questions about session-report

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

FAQPage Schema

How do I generate a development session summary from Git history?▼

To generate a development session summary, this Skill analyzes your local Git history and state files to compile a record of code changes, features, and verification results. It automates session summarization by reviewing project context and activity logs.

What is session progress tracking for software engineering?▼

Session progress tracking is the process of visualizing the progress of features through various stages of development. This Skill helps developers keep a record of accomplishments and plan next steps by summarizing project context and activity logs.

Do I need local Git history to track my project review?▼

Yes, you need local Git history and state files to track your project review. The Skill relies on these local repositories to automatically compile a summary of your work, including code changes and decisions made during the session.

Can I automate code analysis reporting for my development sessions?▼

You can automate code analysis reporting by running this Skill to generate a concise summary of your current session. It analyzes project context and activity logs to present features, code changes, and verification results directly for planning.

What's the best way to summarize code changes for future planning?▼

The best way to summarize code changes for future planning is to use an automated session report tool that analyzes local Git history. It extracts features, verification results, and decisions to aid in decision-making for future sessions.

What are the limitations of using local state files for session reporting?▼

A limitation of using local state files for session reporting is that the Skill relies entirely on local Git history and state files to compile a summary. It cannot track development progress or code changes if local project context and activity logs are unavailable.