skills.rest
muselesscreator
muselesscreatorCOMMUNITY
Explore all skills by this author →
GitHub

savepoint

Summarizes the current conversation into a handoff file for a fresh session.

Updated Apr 9, 2026
Search Tags:#git#context management#handoff#checkpoint#ai workflow#session summary#conversation resume
One-click install
npx skills add https://github.com/muselesscreator/ui-skills --skill savepoint-muselesscreator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: savepoint
Source: https://github.com/muselesscreator/ui-skills/tree/main/savepoint
Command: npx skills add https://github.com/muselesscreator/ui-skills --skill savepoint-muselesscreator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI coding sessions eventually hit context limits, forcing compaction or a fresh session that loses all accumulated decisions, constraints, and progress. This Skill captures the full working state into a dense handoff file so a fresh agent can resume with zero memory of the prior session. ## Core Features & Use Cases - Structured Handoff Generation: Writes a markdown file capturing goal, verbatim constraints, state, decisions, key files, next steps, and open questions. - Git-Aware Organization: Stores handoffs per repository and branch under ~/.claude/skill-output, with a handoff-latest.md symlink for quick access. - Proactive Context Management: Designed to run around 150k tokens of context use, before auto-compact fires, pairing with /clear for a true context reset. - Use Case: You have been debugging a feature for hours and your context is nearly full. Run the savepoint command, clear the session, and a fresh agent reads the handoff file to continue exactly where you left off. ## Quick Start Ask the agent to save a savepoint of the current session so you can resume the work in a fresh conversation.

Frequently Asked Questions about savepoint

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

FAQPage Schema
How do I hand off an AI coding session to a fresh conversation?▼

Run the savepoint command to write a handoff file capturing goal, decisions, key files, and next steps. Then clear the context and have the new session read the handoff-latest.md file to resume.

When should I save a session checkpoint before context runs out?▼

Save around 150k tokens of context use, before auto-compact fires. This lets you clear the session fully and reload only the dense handoff file instead of keeping a verbose compaction summary resident.

Where are handoff files stored on disk?▼

Handoffs are written to ~/.claude/skill-output/<repo>/<branch>/ with a timestamped filename, plus a handoff-latest.md symlink pointing to the most recent one for that repository and branch.

Does savepoint modify code or run tests during handoff?▼

No. It is read-and-write only for the handoff file itself: it runs git status and git log for a state check but performs no edits, linting, or commits on the codebase.

What happens to code that exists only in the conversation?▼

Proposed diffs or snippets not yet written to disk are captured in the Key Files section of the handoff, since a fresh agent can re-read the repo but cannot recover unwritten work.

Related Skills

Explore More Software Engineering Skills→
robritacca-dotcomrobritacca-dotcom
1

land

Triages and merges all pending git branches, worktrees, and stashes into a local main.

Community
Advanced
FlorianBruniauxFlorianBruniaux
5.9k

handoff-resume

Loads a handoff document and resumes work from a previous session's state.

Community
Basic
oElberteoElberte

git-workflow

Verify working-tree state and enforce staging and commit hygiene.

Community
Intermediate
FrogAiFrogAi
1

save-state

Save the current Codex session state to a JSON snapshot in ~/.codex/compact-saves/.

Community
Intermediate