skills.rest
Jia-Hong-Peng
Jia-Hong-PengCOMMUNITY
Explore all skills by this author →
GitHub

checkpoint

Save and resume git state, decisions, and remaining work items.

Updated Feb 24, 2026
Search Tags:#git#workflow#context#resume#checkpoint#session#state
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill checkpoint-jia-hong-peng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/checkpoint
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill checkpoint-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of losing development context when switching between branches, workspaces, or taking long 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 mental overhead.

Core Features & Use Cases

  • State Capture: Records git branch, status, diff statistics, recent commits, and conversation history.
  • Decision Logging: Documents architectural choices, trade-offs, and approaches taken during the session.
  • Resume Guidance: Provides concrete next steps, notes, and artifact recovery for future sessions.
  • Use Case: You are halfway through refactoring the authentication module when a production issue requires an immediate branch switch. Run the checkpoint skill to save your progress, then resume later on any branch or machine with full context restored.

Quick Start

Use the checkpoint skill to save your current working state before switching branches or taking a break.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I save git state and development context before switching branches?▼

To save git state before switching branches, you can capture your current working state including git status, recent commits, and architectural decisions. This records your session artifacts and remaining work items so you can resume exactly where you left off without mental overhead.

What is the best way to resume work state across sessions after a long break?▼

Resuming work state across sessions involves restoring a previously saved checkpoint that contains your git diff statistics, conversation history, and remaining tasks. This provides concrete next steps and artifact recovery to fully restore your development context.

Can I use this checkpoint skill to handoff workspace context to another machine?▼

Yes, you can use this checkpoint skill to handoff workspace context to another machine. It captures your git branch, status, and architectural choices into session artifacts, allowing you to resume your development workflow on any branch or machine with full context restored.

Does this checkpoint skill require specific git tool access to record session artifacts?▼

Yes, the checkpoint skill requires Bash, Read, Write, Glob, Grep, and AskUserQuestion tool access to execute git commands, record session artifacts, and restore context upon resume. These tools are necessary to capture your full working state and architectural decisions.

How does decision logging work when saving development context for branch switching?▼

Decision logging for branch switching works by documenting architectural choices, trade-offs, and approaches taken during your session. This ensures that when you resume work state, the reasoning behind your development context is preserved alongside your git changes and remaining work items.

Related Skills

Explore More Software Engineering Skills→
vib795vib795

checkpoint

Save and resume repository state with git branch, logs, and work plan.

Community
Advanced
ArtRivArtRiv

gsd-resume-work

Restore STATE.md and checkpoint markers to resume interrupted project workflows.

Community
Intermediate
gerald-icagerald-ica

git-pushing

Automate staging, committing, and pushing git changes to a remote branch.

Community
Intermediate
shellicarshellicar

git-knowledge

Explain Git working tree, index, and commit states to determine when stashing is required.

Community
Basic