checkpoint

Save and resume working state checkpoints as timestamped Markdown files.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/bajajvinamr/little-wins --skill checkpoint-bajajvinamr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack/checkpoint
Command: npx skills add https://github.com/bajajvinamr/little-wins --skill checkpoint-bajajvinamr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and persist full working context so future sessions can resume exactly where you left off. It records git state, decisions made, and remaining work, enabling handoffs across branches and workspace switches.

Core Features & Use Cases

  • Checkpoint save: captures git status, diffs, recent logs, and uncommitted changes.
  • Resume: loads the latest checkpoint and reconstructs the working context, including decisions and remaining tasks.
  • Cross-branch handoff: preserves and transfers context between branches or workspaces to avoid duplicated effort.

Quick Start

Save the current working state as a new checkpoint with an automatically inferred title.

Frequently Asked Questions about checkpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save my git workflow state before switching branches?

You can resume work after a session handoff by loading the latest checkpoint file. This reconstructs your working context, including git state, decisions made, and remaining tasks, so you can pick up exactly where you left off.

What is the best way to transfer working context across branches?

The best way to transfer working context across branches is to save a checkpoint that records your git state and decisions. This preserves context during workspace switches to avoid duplicated effort when resuming work.

Can I use checkpoint files to trace decisions made during a project?

Yes, you can use checkpoint files to trace decisions made during a project. Checkpoints are stored as timestamped Markdown in the project's checkpoints directory, enabling easy resumption and traceability of your git state and workflow history.

Does this skill require any external dependencies to save session artifacts?

No, this skill requires no external dependencies to save session artifacts. It independently captures your git state, decisions, and remaining work, storing them as self-contained Markdown files within your project's checkpoints directory.