session-checkpoint
Skill0 starsChanged 7 months agoMITView on GitHub
Mid-session checkpoint: save progress to MEMORY.md, update active plan status, write/append session summary, and note lessons learned — then continue working. Use when switching focus areas or after completing a major milestone within a session.
- Commits and pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- AlexZio00/sovereign-skillstheir own version, first seen Nov 14, 2026
- Brandondaymdr/Claude-Skillstheir own version, first seen Oct 29, 2026
- jin2004-cmd/codex-practical-skillstheir own version, first seen Oct 13, 2026
- xarleyn/dsh-pluginstheir own version, first seen Oct 8, 2026
- herreraspaintingba-hub/second-brain-starter-kittheir own version, first seen Oct 2, 2026
- NITISH-R-G/agent-memory-protocoltheir own version, first seen Aug 1, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- AlexZio00/sovereign-skills★ 158same name
- tunsuy/ai-skills★ 4same name
- xarleyn/dsh-plugins★ 3same name
- Brandondaymdr/Claude-Skills★ 1same name
- jin2004-cmd/codex-practical-skills★ 1same name
- NITISH-R-G/agent-memory-protocol★ 1same name
- herreraspaintingba-hub/second-brain-starter-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- application-trackerSkill
- applySkill
- cold-outreachSkill
- company-deep-diveSkill
- contact-populationSkill
- job-searchSkill
- meeting-prepSkill
- onboard-userSkill
- resume-tailorSkill
- session-endSkill
- session-startSkill
- warm-followupSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
If lessons found: add to MEMORY.md "Lessons Learned" section immediately (no approval needed for memory — it's internal).
- Distinctive: line 31
If rule/skill updates needed: note them but ASK the user before modifying rules/skills.
- Very specific: line 35
Update the project's MEMORY.md (path is OS-specific — see docs/SETUP.md.
- Distinctive: line 37
Update "Next Session Priorities" to reflect the current state.
- Distinctive: line 38
Update any infrastructure / MCP changes.
- Distinctive: line 39
Update project status sections.
- Very specific: line 44
Check MEMORY.md for plan references.
- Distinctive: line 45
Read the plan file.
- Distinctive: line 47
Update "Resume at" to the current position.
- Very specific: line 64
If your remote requires PAT-in-URL: use the pattern documented in docs/SETUP.md (set token → push → strip token).
- Very specific: line 68
If a session summary exists for today (plans/archive/SESSION-SUMMARY-{user-slug}-YYYY-MM-DD.md):
- Distinctive: line 70
Use suffix letters if multiple summaries exist (a, b, c, d…).
- Distinctive: line 72
If no summary exists yet, create one with the checkpoint format:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Session Checkpoint
Mid-session save point that preserves all context without ending the session.
How It Differs From Session End
| Checkpoint | Session End |
| Saves progress, keeps working | Saves progress, wraps up |
| Appends to existing session summary | Creates final session summary |
| No "ready to restart" message | Tells user safe to restart |
| Git commit + push (sync) | Full file-state review + git push |
| Quick (2-3 min) | Thorough (~5 min) |
Workflow
Step 1: Quick lessons check
Scan the session since the last checkpoint (or session start) for:
- Technical discoveries worth remembering
- Rule/skill updates needed
- Mistakes to prevent next time
If lessons found: add to MEMORY.md "Lessons Learned" section immediately (no approval needed for memory — it's internal).
If rule/skill updates needed: note them but ASK the user before modifying rules/skills.
Step 2: Update MEMORY.md
Update the project's MEMORY.md (path is OS-specific — see docs/SETUP.md; on Claude Code it lives at ~/.claude/projects/<project-hash>/memory/MEMORY.md).
- Update "Next Session Priorities" to reflect the current state.
- Update any infrastructure / MCP changes.
- Update project status sections.
- Keep under 200 lines.
Step 3: Update active plan (if any)
Check MEMORY.md for plan references. If an active plan exists:
- Read the plan file.
- Mark completed steps (
⬜→✅). - Update "Resume at" to the current position.
- Note any new decisions or blockers.
Step 4: Git commit + push
Sync all changes to GitHub. The repo is a public template (or your private fork) — commit and push.
git add -A
git status --short
git commit -m "Checkpoint $(date +%Y-%m-%d): <brief summary of work since last checkpoint>"
# Push (uses whatever auth you have configured: SSH key, credential cache, or PAT-in-URL pattern documented in docs/SETUP.md).
git push origin mainIf your remote requires PAT-in-URL: use the pattern documented in docs/SETUP.md (set token → push → strip token). NEVER leave a PAT in the remote URL.
Step 5: Append to session summary
If a session summary exists for today (plans/archive/SESSION-SUMMARY-{user-slug}-YYYY-MM-DD.md):
- Append a new checkpoint section with what was accomplished since the last save.
- Use suffix letters if multiple summaries exist (a, b, c, d…).
If no summary exists yet, create one with the checkpoint format:
# Session Summary — {user-slug} — YYYY-MM-DD[suffix]
## Checkpoint 1: HH:MM / [milestone]
### Done
- [What was completed]
### Status
- [Current state of work]
### Next (continuing this session)
- [What we're doing next]Save to: plans/archive/SESSION-SUMMARY-{user-slug}-YYYY-MM-DD[suffix].md.
Step 6: Confirm and continue
Output a brief status line:
Checkpoint saved. Continuing with [next focus area].Then immediately proceed with whatever work comes next — do NOT wait for user input unless there's an unresolved question.
Rules
- Be fast — this is a mid-session save, not a full wrap-up. 2-3 minutes max.
- NEVER skip MEMORY.md — always update, even if minor.
- Append, don't overwrite — add to the existing session summary, don't replace it.
- Don't ask unnecessary questions — save and move on.
- Always update active plan — if one exists, mark progress.
- Keep it brief — short bullets, not paragraphs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

