checkpoint

Record git state, decisions, and remaining tasks into resumable checkpoints.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mgher668/surf-ai --skill checkpoint-mgher668
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/mgher668/surf-ai/tree/main/.agents/skills/gstack/checkpoint
Command: npx skills add https://github.com/mgher668/surf-ai --skill checkpoint-mgher668

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and resume working state checkpoints. Capture git state, decisions made, and remaining work so you can pick up exactly where you left off — even across Conductor workspace handoffs between branches.

Core Features & Use Cases

  • Save and resume checkpoints across branches and contexts.
  • Capture git state, major decisions, and remaining work to maintain continuity.
  • Proactively suggest checkpointing before a session ends or a context switch.
  • Use to hand off work between team members or branches without losing progress.

Quick Start

Save a checkpoint now to capture your current state and resume later from where you left off.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I save and resume my git work state across different branches?

To save and resume your git work state across branches, you can record a checkpoint that captures your current git state, major decisions, and remaining tasks. This allows you to restore your working context exactly where you left off after a context switch.

What is the best way to maintain workflow continuity during a git context switch?

The best way to maintain workflow continuity during a git context switch is by proactively saving a checkpoint before you switch. This records your session state and remaining work, ensuring no progress is lost when handing off between branches.

Can I use checkpointing to hand off work between team members without losing progress?

Yes, you can use checkpointing to hand off work between team members without losing progress. By saving your session state, including git details and decisions, another member can resume the work exactly from your recorded point.

How does proactive state management work before a session ends?

Proactive state management prompts you to save a checkpoint before your session ends or a context switch occurs. This ensures your current git state and remaining tasks are recorded automatically for later resumption.

Do I need slash commands to save and restore my session state?

You do not strictly need slash commands to save and restore your session state, as proactive prompting handles it automatically. However, slash commands are supported to manually save or resume your work state whenever needed.

When should I avoid relying on session checkpoints for state management?

You should avoid relying on session checkpoints if your workflow does not involve context switches, branch handoffs, or interrupted sessions. It is designed for saving and resuming complex state, not for simple linear tasks without interruptions.