save-session

Write a dated session file with project context and decision indexes.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill save-session-buvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-session
Source: https://github.com/buvis/home/tree/main/.claude/skills/save-session
Command: npx skills add https://github.com/buvis/home --skill save-session-buvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write structured session files at the end of a work session to preserve context for later resumption, preventing loss of decisions, context, and next steps.

Core Features & Use Cases

  • Automatic derivation of the project name from the current directory to organize per-project session history.
  • Structured session state synthesis that captures goals, what worked, what failed, decisions made, and explicit next steps.
  • Writes to a standard location (~/.claude/session-data/YYYY-MM-DD-<project-name>-session.md) with collision handling, and updates both project-level and global decision indexes.

Quick Start

End the current session and run the Save Session command to create a dated session file under ~/.claude/session-data.

Frequently Asked Questions about save-session

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

FAQPage Schema
How do I preserve session context and decisions before ending a work session?

Session context preservation saves your current project state by writing a structured file that captures goals, decisions, and next steps. This enables seamless resumption later without losing decisions or context.

How do I save session notes to a specific project directory automatically?

Saving session notes automatically derives the project name from your current working directory (CWD) to organize per-project session history. Files are written to a standard dated path under the project's session data.

What's the best way to maintain a decision index across multiple projects?

Maintaining a decision index across multiple projects involves updating both project-level and global records when saving a session. This enforces an end-to-end workflow that tracks decisions made during each work period.

Can I archive workflow notes without losing the next steps I planned?

Archiving workflow notes with this approach explicitly captures planned next steps in the structured session file. The session state synthesis records goals, decisions, and next steps so nothing is lost when you resume later.

Does session management handle file name collisions when saving multiple sessions per day?

Session management includes collision handling when writing to the standard dated path under ~/.claude/session-data. This ensures multiple sessions saved on the same day do not overwrite each other's context files.