checkpoint

Create, store, and recover work state checkpoints via the Conductor platform.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/SoSoBurner/GStack --skill checkpoint-sosoburner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/SoSoBurner/GStack/tree/main/checkpoint
Command: npx skills add https://github.com/SoSoBurner/GStack --skill checkpoint-sosoburner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of saving and resuming your work state, ensuring that you can pick up right where you left off, even across workspace handoffs.

Core Features & Use Cases

  • Checkpoint Creation: Automatically capture your current git state and decisions made.
  • Checkpoint Retrieval: Easily retrieve your saved checkpoints and resume your work.
  • Proactive Suggestions: Prompt users to save checkpoints before ending a session or switching context.
  • Session Recovery: Support recovery of context for a project after compaction or session start.

Quick Start

Run the /checkpoint command to save your current state.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I save my work state and resume progress across git sessions?

To save your work state and resume progress across git sessions, run the `/checkpoint` command to automatically capture your current git state and decisions. You can retrieve these saved checkpoints later to resume your work exactly where you left off.

What is the best way to recover context after a session compaction or workspace handoff?

Recovering context after session compaction or workspace handoff is handled by checkpoint retrieval. The Skill stores your previous git state and decisions, allowing you to resume your project seamlessly when starting a new session or switching branches.

Can I use checkpointing to manage git state and decisions on the Conductor platform?

Yes, you can use checkpointing to manage git state on the Conductor platform. The Skill requires access to your git repository and Conductor workspace to create, store, and recover your work state checkpoints effectively.

When should I save a checkpoint before ending a session or switching context?

You should save a checkpoint before ending a session or switching context when you have made significant progress or decisions. The Skill proactively prompts you to save checkpoints at these moments to prevent losing your current work state.

Does checkpointing work without direct access to my git repository?

No, checkpointing does not work without access to your git repository. The Skill requires direct access to your git repository and Conductor workspace to automatically capture your current state and manage checkpoint storage.

Why do I need to save progress manually instead of relying on automatic session recovery?

You need to save progress manually via the `/checkpoint` command to ensure specific decisions and git states are captured. While the Skill supports session recovery, proactive checkpointing guarantees your exact work state is stored before handoffs or compaction.