Context Checkpoint

VerifiedSafe

Automatically saves critical context to a checkpoint file before context resets. It preserves task progress, learnings, and next priorities, allowing 50-70% token savings when used with /compact or /clear commands. Best used every few tasks or before switching feature areas.

Sby Skills Guide Bot
ProductivityIntermediate
1206/2/2026
Claude Code
#context-management#checkpoint#token-saving#claude-code

Recommended for

Our review

Saves context state to reduce token consumption when using Claude Code.

Strengths

  • Saves 40 to 70% of tokens depending on the command used.
  • Allows easy resumption after a /clear.
  • Structures important information (progress, learnings).

Limitations

  • Requires manual discipline to trigger checkpoints.
  • Does not preserve file contents or error traces.
  • Only works with Claude Code.
When to use it

Use this skill every 3 tasks or before switching domains to save tokens.

When not to use it

Avoid if you prefer automatic context management or if your sessions are very short.

Security analysis

Safe
Quality score85/100

The skill only reads/writes local files for checkpointing context; no network, shell, or destructive actions.

No concerns found

Examples

Save checkpoint before clearing
Save a context checkpoint now. I want to reclaim tokens before clearing the session.
Checkpoint after completing a task
I just finished fixing the login bug. Create a checkpoint summarizing what we did and what's next.
Restore from checkpoint
Read the checkpoint file and restore our session context so we can continue working.

name: checkpoint description: Save context state - auto-triggered every 5 tasks allowed-tools: Read, Write, TaskList, Grep model: sonnet user-invocable: false

Context Checkpoint

Save critical context before /clear. Enables 50-70% token savings.

When to Checkpoint

  • Every 3 tasks (aggressive - preserves tokens)
  • Before switching feature areas
  • After resolving complex bugs
  • When response feels slow (context bloat sign)

Checkpoint Format

Write to .claude/checkpoint.md:

# Checkpoint: [TIMESTAMP]

## Sprint Status
[Sprint X: N/M complete]

## Completed This Session
- [Task]: [what was done]

## Key Learnings
- [Bug pattern]: [resolution]

## Next Priority
[Next task ID and title]

## Files Modified
- [file paths]

After Saving

Tell user:

💾 Checkpoint saved.

Run /compact now to reclaim ~40% tokens (keeps context summary).
Use /clear only at major transitions (reclaims ~70% but wipes context).

Auto-Restore

After /clear, read .claude/checkpoint.md and continue.

What to Preserve

| Keep | Skip | |------|------| | Task progress | File contents | | Learnings | Error traces | | Next priority | Tool call logs |

Token Savings

| Command | Savings | Use When | |---------|---------|----------| | /compact | ~40% | Default after checkpoint | | /clear | ~70% | Major transitions, sprint end |

Rule: /compact after every checkpoint. /clear at major transitions.

Related skills