st0nefish/session-checkpoint

PROACTIVELY invoke this (without being asked) after completing a major task, stage, or milestone, or when context window usage is approaching full.

Commits staged/unstaged changes and posts structured context to the linked issue.

Steps

1. Gather current state: inspect the current branch, default branch, recent commits, changed files, and any linked issue directly with git and native host tooling.

2. Infer what's in progress and what should come next from conversation context. When auto-triggering, do NOT ask — infer from the conversation. Only use AskUserQuestion if explicitly invoked and progress is genuinely unclear.

3. Compose the checkpoint comment content with these sections:

   === CHECKPOINT ===
   Branch: <branch>
   Timestamp: <ISO 8601>
   
   === NEXT STEPS ===
   - <what to pick up next>
   
   === KEY CONTEXT ===
   - <decisions, gotchas, important state that shouldn't be lost>
   

4. Commit any uncommitted changes:

   git add -A
   git commit --no-verify -m "checkpoint: <brief description of progress>"
   

   If there are no changes to commit, skip the commit step but still post the issue comment. Only push if the user explicitly asked to publish the checkpoint or has already approved pushing in this session.

5. If the current branch matches type/NNN-*, post the checkpoint as an issue comment:

   • on GitHub repos, prefer gh issue comment <N> with the body from step 3
   • otherwise use the equivalent host-native issue-comment command if available
   • use stdin or a heredoc rather than relying on plugin helper-script paths

6. Briefly confirm: checkpoint committed and (if applicable) posted to issue #N. When auto-triggering, keep to one line. When user-invoked, mention /session:session-resume to continue from this point.