skills.rest
sujithatzackriya
sujithatzackriyaCOMMUNITY
Explore all skills by this author →
GitHub

save-session

Persist session state into progress.txt with append-or-update patches.

Updated Aug 23, 2026
Search Tags:#git workflow#session management#progress tracking#diff preview#documentation updates#todo lists#atomic file writes
One-click install
npx skills add https://github.com/sujithatzackriya/skills --skill save-session-sujithatzackriya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save-session
Source: https://github.com/sujithatzackriya/skills/tree/main/skills/save-session
Command: npx skills add https://github.com/sujithatzackriya/skills --skill save-session-sujithatzackriya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save-session prevents lost context between work sessions by persisting what you completed, what you discovered, and what remains, in the correct progress.txt file.

Core Features & Use Cases

  • Progress persistence with guardrails: Snapshots completed TODOs, newly emerged TODOs, findings/gotchas, and refreshes CURRENT STATUS with today’s date.
  • Append-or-update behavior: Never overwrites historical sections; only CURRENT STATUS is replaced.
  • Diff-first, atomic write: Shows a proposed diff for confirmation and writes atomically via a temp file to keep progress.txt and commit decisions aligned.
  • Correct integration with companion skills: Works alongside /resume-session, /context, and /commit so session lifecycle stays consistent.

Quick Start

Run save-session by telling your agent to snapshot your work, for example: /save-session "finished auth refactor; refresh-token still pending".

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 git workflow progress before stepping away from a project?▼

Session state persistence prevents lost work context by recording completed TODOs, new TODOs, gotchas, and an updated current status into progress.txt. It uses an append-or-update patch with a diff preview and writes atomically, ensuring historical sections are never overwritten.

How do I update progress.txt with completed TODOs and new findings without losing history?▼

Yes, the save-session process requires a diff preview before writing. It constructs a proposed diff for confirmation and writes atomically via a temp file, keeping your progress.txt updates and commit decisions aligned without auto-creating or performing any git commits.

Does save-session work with resume-session and other session lifecycle skills?▼

To use save-session, simply tell your agent to snapshot your work, for example: /save-session "finished auth refactor; refresh-token still pending". The Skill then locates the correct progress.txt target, constructs the append-or-update patch, and performs the atomic write.

Why does saving session state require an atomic write and diff preview?▼

Save-session does not auto-create or perform git commits. It strictly persists session state into progress.txt by recording completed TODOs, new TODOs, gotchas, and refreshing CURRENT STATUS, leaving all commit decisions to companion skills or manual execution.

Related Skills

Explore More Software Engineering Skills→
minhcopilotminhcopilot
1

session-resume

Restore prior session context from local repository data and generate summaries.

Community
Basic
TumeloRamaphosaTumeloRamaphosa

context-save

Capture git state, decisions, and remaining work into checkpoint artifacts.

Community
Basic
CivicActionsCivicActions
2

handoff-message

Generate a structured handoff document capturing progress, file changes, and pending tasks.

Official
Intermediate
HugopeckHugopeck

update-skills

Refresh installed Track skill clones with fast-forward-only git pulls.

Community
Intermediate