session-summary

Generate a markdown session summary with actions, decisions, blockers, and next steps.

22|6|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/felvieira/claude-skills-fv --skill session-summary-felvieira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-summary
Source: https://github.com/felvieira/claude-skills-fv/tree/main/skills/31-session-summary
Command: npx skills add https://github.com/felvieira/claude-skills-fv --skill session-summary-felvieira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers lose critical context when switching tasks or handing off work, leading to duplicated effort and missed decisions. This Skill creates a concise, structured summary of a coding session to preserve actions, artifacts, decisions, blockers, and next steps.

Core Features & Use Cases

  • Consolidates all actions performed during a session.
  • Lists created or modified artifacts with status.
  • Captures key decisions, pending items, and prioritized next steps.
  • Generates markdown files in docs/context for easy reference.
  • Ideal for ending a session, transferring work to another developer, or resuming after a pause.

Quick Start

Ask the assistant to generate a session summary for today’s work and save it to the docs/context folder.

Frequently Asked Questions about session-summary

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

FAQPage Schema
How do I generate a development session summary for a git handoff?▼

To generate a development session summary, the Skill analyzes your session logs and git history to capture actions, artifacts, decisions, blockers, and next steps, saving the handoff context as a markdown file.

What is the best way to document coding session context for another developer?▼

Documenting coding session context involves creating a structured summary of actions, artifacts, and decisions, which this Skill automatically writes to the docs/context directory as markdown files for easy reference.

Does this session handoff tool require access to git history?▼

Yes, generating session handoff summaries requires access to your session logs and git history, alongside the ability to write markdown files to the docs/context directory.

Can I save session context to markdown files automatically?▼

Yes, you can save session context automatically by asking the assistant to generate a summary, which creates structured markdown files in the docs/context directory to preserve actions and next steps.

What should a session handoff summary include to preserve context?▼

A session handoff summary should include performed actions, created or modified artifacts with status, key decisions, blockers, and prioritized next steps to prevent duplicated effort when resuming or transferring work.