checkpoint

Capture git branch, uncommitted changes, decisions, and remaining tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing development context when switching sessions, branches, or workspaces. It captures the full working state so you can resume exactly where you left off without manual reconstruction.

Core Features & Use Cases

  • Git State Capture: Records current branch, uncommitted changes, and recent commit history.
  • Decision Logging: Documents architectural choices and trade-offs made during the session.
  • Progress Tracking: Lists remaining work and next steps in priority order.
  • Cross-Session Resume: Restores full context even across different branches or Conductor workspace handoffs.

Quick Start

Use the checkpoint skill to save your current working state before 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 git workflow context before ending a development session?

To save git workflow context before ending a development session, capture your current branch, uncommitted changes, recent commit history, decisions, and remaining tasks. This records the full working state for deterministic context recovery.

What is the best way to resume a git branch handoff without manual reconstruction?

The best way to resume a git branch handoff without manual reconstruction is to restore a previously captured session state. This includes your exact branch, architectural decisions, and prioritized next steps for seamless cross-session recovery.

Does context recovery work across different Conductor workspaces?

Yes, context recovery works across different Conductor workspaces. It restores full context including git state and progress tracking even across different branches or workspace handoffs, satisfying deterministic recovery requirements.

How do I track remaining development tasks and architectural decisions?

To track remaining development tasks and architectural decisions, log the trade-offs made during your session and list remaining work in priority order. This ensures progress tracking captures everything needed to continue.

Why do I lose development context when switching git branches?

You lose development context when switching git branches because uncommitted changes and undocumented decisions are not automatically saved. Capturing the complete working state prevents this loss without relying on manual memory reconstruction.