checkpoint

Capture and restore git working state with decisions and tasks.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill checkpoint-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/checkpoint
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill checkpoint-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing development context when switching branches, ending sessions, or taking breaks. It captures the full working state including git changes, decisions made, and remaining tasks so you can resume exactly where you left off without missing a beat.

Core Features & Use Cases

  • State Capture: Records git branch, status, diff statistics, recent commits, and conversation context into a persistent checkpoint.
  • Context Recovery: Restores the exact working state including decisions, remaining work, and notes for future sessions.
  • Use Case: You are refactoring the authentication module, switch to a hotfix branch for 20 minutes, then resume with all architectural decisions and next steps preserved.

Quick Start

Use the checkpoint skill to save your current working state before switching branches or ending your session.

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 working state before switching branches?

To save your git working state before switching branches, you can capture the current branch, status, diff statistics, and recent commits into a persistent checkpoint. This preserves your exact development context and remaining tasks for later restoration.

What is the best way to resume a development session after a context switch?

The best way to resume a development session after a context switch is to restore a previously saved checkpoint. This recovers the exact working state, including architectural decisions and notes, allowing you to continue exactly where you left off.

Does this checkpoint tool require a specific git repository setup?

Yes, this checkpoint tool requires integration with git repositories and local filesystem storage. It relies on these dependencies to persist checkpoint artifacts and timeline events necessary for capturing and restoring your complete working state.

Can I hand off my current workspace state to another team member?

Yes, you can hand off your current workspace state to another team member. The tool captures complete working state context for workspace handoffs, preserving git changes, decisions made, and remaining tasks so the recipient can resume work seamlessly.

What context is lost when ending a software development session without a checkpoint?

Without a checkpoint, you risk losing development context when ending a software development session, including git changes, architectural decisions made, and remaining tasks. This makes it difficult to resume your work without missing a beat.

When should I avoid using git checkpoints for session management?

You should avoid using git checkpoints for session management if your workflow lacks git repositories or local filesystem storage. The tool depends on these environments to persist checkpoint artifacts and timeline events for capturing and restoring state.