save-session

Write structured session history markdown into a project-scoped docs/history directory.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/CopeeeTang/copeee-skills --skill save-session-copeeetang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-session
Source: https://github.com/CopeeeTang/copeee-skills/tree/main/skills/save-session
Command: npx skills add https://github.com/CopeeeTang/copeee-skills --skill save-session-copeeetang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents losing important decisions, prompts, and next steps by capturing a compact, structured action-route summary before Claude Code compacts the conversation or you end the session.

Core Features & Use Cases

  • Structured session action-route capture: Extracts key prompts,思路,探索方向,执行结果, and writes them into docs/history/ for later review.
  • Project-scoped round history: Organizes outputs by project name and round number (round_{N}.md) to keep multiple sessions traceable.
  • Sub-agent writing to avoid token bloat: Uses an agent subprocess so the main context stays lean while the markdown is generated and saved.

Quick Start

Run /save-session my-project when you are about to end the conversation or when the context is getting full to automatically write a session history file to docs/history/my-project/round_N.md.

Frequently Asked Questions about save-session

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

FAQPage Schema
How do I save my conversation context before Claude Code compacts the session?

To save conversation context before compaction, run /save-session with an optional project name to generate a structured markdown history file. This captures key prompts, decisions, and next steps into a project-scoped docs/history directory.

How do I preserve action plans and workflow continuity across multiple coding sessions?

Preserve workflow continuity by running /save-session to write a structured action-route summary into docs/history. It organizes outputs by project name and round number, keeping multiple sessions traceable for later review.

What is context compaction and when do I need to save my session history?

Context compaction reduces conversation context size to fit token limits. Save your session history when context is near compaction, when ending a session, or explicitly via /save-session to avoid losing important decisions and next steps.

Does generating a session summary consume my main context window tokens?

Generating a session summary does not bloat the main context window. The Skill uses a sub-agent subprocess to handle the deterministic file generation, ensuring the main context stays lean while the markdown is written.

How do I organize session summaries for different projects and workflow rounds?

Organize session summaries by running /save-session with a project name. It automatically creates a structured markdown file named round_N.md inside the docs/history/my-project directory, separating outputs by project and round number.

Can I manually trigger a session history save without ending the conversation?

You can manually trigger a session history save at any time by running /save-session with an optional project name. It writes the structured action-route markdown into the project workspace history directory immediately.