save-session

Writes a concise markdown summary of the current working session to docs/tmp.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill save-session-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save-session
Source: https://github.com/pnewsam/skills/tree/main/archive/save-session
Command: npx skills add https://github.com/pnewsam/skills --skill save-session-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a working session ends, the reasoning behind decisions, debugging paths, and rejected alternatives is lost. This Skill captures that narrative as a searchable markdown handoff file so future sessions can reference what was done and why. ## Core Features & Use Cases - Structured Session Summaries: Generates a markdown file with sections for problem, actions taken, key decisions, outcome, files touched, and follow-ups. - Depth Scaling: Adapts the summary length to the session type, from a five-line quick fix note to a full debugging or architecture write-up. - Safe Local Writes: Only creates or appends files in docs/tmp, never commits or pushes, and reports whether the note is tracked, untracked, or ignored by Git. - Use Case: After a long debugging session that traced a pagination bug to an off-by-one cursor, ask for a session save to preserve the diagnosis path and root cause for future reference. ## Quick Start Use the save-session skill to summarize this working session and save it as a markdown handoff in docs/tmp.

Frequently Asked Questions about save-session

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

FAQPage Schema
How do I save a summary of my current AI working session?▼

Ask the assistant to save the session, and it will write a markdown summary to docs/tmp using the pattern session-<date>-<slug>.md. The summary covers the problem, actions taken, key decisions, outcome, and files touched.

What should a session handoff note include?▼

A session handoff should include the problem or goal, what was done, key decisions with rationale, the solution or outcome, files touched, and any open follow-ups. Sections with nothing meaningful to say are omitted rather than left as placeholders.

Does saving a session summary commit anything to git?▼

No, the skill only writes local files in docs/tmp and never commits or pushes. After writing, it checks git status and reports whether the note is tracked, untracked, or ignored.

Can I save a session summary mid-task before the work is finished?▼

Yes, you can save a checkpoint mid-session with the status set to in-progress, noting what has been done so far. The summary can be updated later or followed by a new summary when the work completes.

What happens if a similar session summary already exists?▼

The skill reads the existing file first and either appends a new dated section for a continuation or creates a new file with a numeric suffix like -2. Tightly related sessions are kept in a single file for easier reference.