session-save

Generate template-compliant session summaries and save them to ai-context/sessions with date-based numbering.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/elfrucool/ai-context-template --skill session-save-elfrucool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-save
Source: https://github.com/elfrucool/ai-context-template/tree/main/core/skills/session-save
Command: npx skills add https://github.com/elfrucool/ai-context-template --skill session-save-elfrucool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates repetitive, inconsistent end-of-session documentation by automatically drafting a structured session summary and saving it to the correct ai-context location.

Core Features & Use Cases

  • Auto-numbered session file creation: Detects today’s date, finds the next XX sequence from ai-context/sessions/, and optionally reuses the XX from an existing plan file for the same topic.
  • Topic suggestion from repo + conversation signals: Suggests a kebab-case topic by analyzing git diff paths/status and conversation/plan context, then asks for confirmation or override.
  • Template-driven summary generation with guardrails: Produces a structured summary (overview, decisions, technical details, current state, follow-up/TODO) aligned to the Development Process guideline and always asks before saving.

Quick Start

Ask your AI agent to run /session-save to generate a session summary from your current git changes and save it to the next ai-context/sessions/YYYY-MM-DD-XX-topic.md file after confirmation.

Frequently Asked Questions about session-save

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

FAQPage Schema
How do I automatically generate end-of-session documentation from git diff?

To generate session documentation from git diff, trigger the summary generation command which analyzes your current changes and drafts a structured markdown file. It scans git status and conversation context to build an overview, decisions, and follow-up list before saving.

What is the best way to maintain continuity for multi-session features in AI context?

Maintaining multi-session feature continuity requires saving structured summaries with sequential numbering and topic names. This Skill optionally reuses sequence numbers from existing plan files and saves to the ai-context directory to preserve development history across sessions.

How do I name and number session summary files in a development context?

Session summary files are named using a YYYY-MM-DD-XX-topic format. The system auto-detects today's date, finds the next sequential number by scanning existing files, suggests a kebab-case topic from git paths, and prompts for confirmation before writing.

Can I review the AI-generated session summary before it saves to my repository?

Yes, you can review the AI-generated session summary before saving. The system previews the drafted markdown file containing technical details and TODOs, then explicitly prompts for confirmation or topic override before writing to the ai-context/sessions directory.

Does session summary automation require a specific folder structure?

Session summary automation requires an ai-context/sessions/ directory to store dated markdown files. It scans this path to determine the next sequential number and saves the final generated summary, relying on this structure for organization.