checkpointing

Save session context into agent configuration and checkpoint files.

17|5|Updated Jan 31, 2026

Search Tags:#automation #git #logs #analysis #checkpointing #session-history

Ready to run

npx skills add https://github.com/gaebalai/claude-code-orchestrator --skill checkpointing-gaebalai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkpointing
Source: https://github.com/gaebalai/claude-code-orchestrator/tree/main/.claude/skills/checkpointing
Command: npx skills add https://github.com/gaebalai/claude-code-orchestrator --skill checkpointing-gaebalai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save session context to agent configuration files or create full checkpoint files.

Core Features & Use Cases

Save and organize session history across CLAUDE, Codex, and Gemini contexts.
Generate comprehensive checkpoints with git history, file changes, and CLI consultations.
Skill analysis workflow to extract reusable patterns for future automation.

Quick Start

Run the checkpointing tool to update the session history or generate a full checkpoint with optional analysis.

Frequently Asked Questions about checkpointing

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

FAQPage Schema

How do I save and organize session context for AI coding agents like CLAUDE, Codex, and Gemini?▼

Session context is saved by automating updates to agent configuration files like CLAUDE.md, AGENTS.md, and GEMINI.md. The tool extracts data from git history, file changes, and CLI consultations to persist context across multiple agent environments.

What is the best way to extract reusable patterns from git logs and session history?▼

Extracting reusable patterns from session history is done using the skill analysis workflow. By running the tool in analyze mode, it parses git logs and CLI consultations to surface patterns for future automation and checkpointing.

How do I generate a full checkpoint file with git history and file changes?▼

Generating a full checkpoint file requires running the checkpointing tool with the full mode flag. This captures comprehensive session context including git history, file changes, and CLI tool consultations into checkpoint files.

Do I need a Git repository to create checkpoint files for session history?▼

A local Git repository is required to create checkpoint files. The tool specifically reads accessible logs from the .claude/logs/cli-tools.jsonl path and writes outputs to .claude/checkpoints to function correctly.

Can I update session history across CLAUDE, Codex, and Gemini configurations simultaneously?▼

Session history can be updated simultaneously across CLAUDE, Codex, and Gemini contexts. The tool writes organized context outputs directly to CLAUDE.md, .codex/AGENTS.md, and .gemini/GEMINI.md.

Why does checkpointing fail when .claude/logs/cli-tools.jsonl is missing?▼

Checkpointing fails because the tool depends on reading session logs located at .claude/logs/cli-tools.jsonl. Without this accessible log file in the local Git repository, the tool cannot extract context or generate checkpoint outputs.