1.6 KiB
1.6 KiB
name, description
| name | description |
|---|---|
| checkpoint | Create detailed git commit with comprehensive commit message. Use when the user says /checkpoint, "make a checkpoint", "commit the work with context", "git checkpoint", or after reaching a stable milestone / completing a feature. |
/checkpoint — Full Git + Context Save
Create a detailed git commit with a comprehensive commit message (includes context from the session).
Grok adaptation: This skill wraps the shared ClaudeTools command defined in .claude/commands/checkpoint.md.
When invoked:
- Read the full authoritative instructions with
read_file .claude/commands/checkpoint.md. - Follow the steps for git analysis, staging (
git add -A), drafting the message (often via local Ollama for prose), and committing. - Adapt tools:
run_terminal_commandfor all git and shell steps. Usespawn_subagentif delegating analysis. - Respect CLAUDE.md rules: Coordinator model (you coordinate, delegate big work), no emojis, ASCII markers, proper session attribution via identity.
Key parts from the command (see full file for complete details):
Part 1: Git Checkpoint
- git status, git diff, recent log.
- Stage everything with
git add -A. - Draft commit message body (use Ollama if available per identity.json endpoints).
- Commit with good message that captures the "why" and key changes.
- (The command continues with context saving aspects in the full spec.)
After commit, often followed by /sync or part of /scc.
Full workflow, Ollama prompts for the message, and integration with session context are in .claude/commands/checkpoint.md.
This pairs with /save (for the narrative log) and /sync.