save

Capture current thread state into a durable snapshot with Git branch context.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill save-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/save
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill save-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

Mid-session state saving and continuity for active threads, letting you capture what happened, what was decided, and what remains open without altering the project.

Core Features & Use Cases

  • Automatic archiving: preserves previous snapshots and updates a timeline for quick history.
  • Branch-aware context: injects the current Git branch into saves to enable precise reloads across branches.
  • Per-user thread memory: stores saves outside the project repository for personal continuity and safety.

Quick Start

Invoke the save workflow to snapshot the thread's state and update SAVED.md and TIMELINE.md.

Frequently Asked Questions about save

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

FAQPage Schema
How do I save mid-session thread state for later continuity without altering my project repository?

Mid-session thread state is saved by writing a durable snapshot to a per-user saves directory outside your project repository, archiving any existing snapshot and updating a chronological timeline. This captures session continuity without altering the project.

How does branch-aware context work when saving a thread checkpoint?

Branch-aware context works by requiring Git to determine your current branch and injecting that branch context into the saved snapshot. This enables precise thread reloading across different branches later.

Do I need Git to capture and archive thread memory during an active session?

Yes, you need Git installed and available to capture thread memory. The skill requires Git to determine the current branch, which is injected into the save snapshot to enable seamless reloading across branches.

What is the best way to maintain a chronological history of my thread checkpoints?

The best way to maintain checkpoint history is using a dedicated save script that automatically archives previous snapshots and updates a TIMELINE.md file. This provides a quick, chronological history of all saved thread states.

Where are my thread state snapshots stored when I archive a session?

Thread state snapshots are stored in a per-user memory store outside the project repository. Storing saves outside the project ensures personal continuity and safety without modifying the actual project files.