mcpField
C
checkpoint

checkpoint

github.com/identity16Productivity039 installsUpdated 7w ago
Repository

About checkpoint

checkpoint is a session wrap-up skill that routes newly learned information to code comments, repository artifacts, or a personal journal as appropriate. It also updates the project mental model and visit state, while keeping personal notes outside the project repository.

Key features

  1. 01Extract decisions and discoveries from a session
  2. 02Propose code comments for important constraints
  3. 03Prepare rationale for PR or commit descriptions
  4. 04Update a personal journal and project mental model
  5. 05Record the current commit, date, and branch

Use cases

  1. 01Preserve a newly discovered code constraint
  2. 02Document the rationale for a chosen approach and rejected alternatives
  3. 03Capture open questions and work in progress
  4. 04Close a routine session by updating the visit marker

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/identity16/skills --skill checkpoint

After installing, type/checkpointin Claude Code to confirm it loaded.

Details

From the project README

checkpoint

Write-side twin of lets-work. Captures what this session taught the user, promoting each item as far up the ladder as it can go: code first, repo artifacts second, the personal store last.

Personal state (zero-trace contract)

Same contract as lets-work — keep the two in sync:

  • Root: ${XDG_DATA_HOME:-$HOME/.local/share}/identity16-skills/projects/<repo-id>/
  • repo-id: normalized origin URL slug (strip protocol/credentials/.git; / and : → __); no remote → absolute path slugged the same way.
  • Files: state.json (last-visit marker), dossier.md (mental model; fallback, never a mirror), journal.md (append-only session log).

Never write any of this — or any reference to this skill pack — into the target project's files, commits, PRs, or issues.

The ritual's weight must be proportional to what the session taught. A routine session that produced nothing worth keeping gets no interview: update state.json, confirm in one line, done. The full routing below is for sessions that actually moved the user's understanding.

Steps

  1. Collect candidates: walk back through the session and list what was learned — decisions made, gotchas hit, invariants discovered, assumptions refuted, questions still open, WIP state.
  2. Route each item up the ladder, proposing promotions rather than silently applying them:
    • Code: a non-obvious constraint or "why" the code cannot express → propose a concise comment at the load-bearing spot, following the target project's comment norms.
    • Repo artifacts: the rationale for the approach taken, alternatives rejected → propose adding it to the PR description or the commit message being shipped.
    • Personal journal: project process facts (where discussion happens, how to run things locally), the user's open questions, WIP notes — anything with no home in the repo → append to journal.md under today's date.
  3. Update dossier.md with deltas to the mental model: new or changed invariants, corrected beliefs. Delete entries the codebase now makes obvious — a shrinking dossier means the codebase is improving.
  4. Write state.json with the current commit, date, and branch.
  5. Confirm to the user what went where.

Guardrails

  • Promotions into the repo are normal work product (comments, PR text, commit messages) — but they must never mention this skill pack, the personal store, or its paths.
  • Do not journal what the repo already records (code structure, git history, existing docs).

Comments

Markdown supported