agentleFS
alexmonegropalexmonegrop/job-hunt-os/.claude/skills/session-checkpoint/SKILL.md

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

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
  1. Very specific:

    If lessons found: add to MEMORY.md "Lessons Learned" section immediately (no approval needed for memory — it's internal).

    line 30
  2. Distinctive:

    If rule/skill updates needed: note them but ASK the user before modifying rules/skills.

    line 31
  3. Very specific:

    Update the project's MEMORY.md (path is OS-specific — see docs/SETUP.md.

    line 35
  4. Distinctive:

    Update "Next Session Priorities" to reflect the current state.

    line 37
  5. Distinctive:

    Update any infrastructure / MCP changes.

    line 38
  6. Distinctive:

    Update project status sections.

    line 39
  7. Very specific:

    Check MEMORY.md for plan references.

    line 44
  8. Distinctive:

    Read the plan file.

    line 45
  9. Distinctive:

    Update "Resume at" to the current position.

    line 47
  10. Very specific:

    If your remote requires PAT-in-URL: use the pattern documented in docs/SETUP.md (set token → push → strip token).

    line 64
  11. Very specific:

    If a session summary exists for today (plans/archive/SESSION-SUMMARY-{user-slug}-YYYY-MM-DD.md):

    line 68
  12. Distinctive:

    Use suffix letters if multiple summaries exist (a, b, c, d…).

    line 70
  13. Distinctive:

    If no summary exists yet, create one with the checkpoint format:

    line 72

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Session Checkpoint

Mid-session save point that preserves all context without ending the session.

How It Differs From Session End

CheckpointSession End
Saves progress, keeps workingSaves progress, wraps up
Appends to existing session summaryCreates final session summary
No "ready to restart" messageTells 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:

  1. Read the plan file.
  2. Mark completed steps (⬜ → ✅).
  3. Update "Resume at" to the current position.
  4. 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 main

If 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

  1. Be fast — this is a mid-session save, not a full wrap-up. 2-3 minutes max.
  2. NEVER skip MEMORY.md — always update, even if minor.
  3. Append, don't overwrite — add to the existing session summary, don't replace it.
  4. Don't ask unnecessary questions — save and move on.
  5. Always update active plan — if one exists, mark progress.
  6. Keep it brief — short bullets, not paragraphs.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.