checkpoint-cycle

Generate git-backed session checkpoint manifests with structured fields and drift triage.

1|Updated Jan 14, 2026

Search Tags:#workflow #commit #memory #handoff #manifest #checkpoint #drift

Ready to run

npx skills add https://github.com/Rwb3n/haios --skill checkpoint-cycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkpoint-cycle
Source: https://github.com/Rwb3n/haios/tree/main/.claude/skills/checkpoint-cycle
Command: npx skills add https://github.com/Rwb3n/haios --skill checkpoint-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to recording session decisions and learnings by generating a git-backed checkpoint manifest that can be shared across sessions.

Core Features & Use Cases

Scaffold a manifest for the current session to standardize handoffs.
Populate fields such as load_principles, load_memory_refs, pending, drift_observed, and completed to capture context and next steps.
Drift gate: surface and triage drift observations before committing, ensuring learnings are reviewed.
Commit workflow: store learnings with ingester_ingest calls and commit changes via session-end and commit-session commands.
Use Case: When ending a work session, generate a reproducible record you can reference in the next session or share with teammates.

Quick Start

Run the checkpoint-cycle skill to scaffold a manifest for the current session.
Populate the manifest fields using ingester_ingest for learnings and fill load_principles, load_memory_refs, pending, and drift_observed.
Execute the commit sequence: just commit-session {session} "<title>" and just session-end {session}.

Frequently Asked Questions about checkpoint-cycle

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

FAQPage Schema

How do I capture session checkpoints for reproducible handoffs?▼

To capture session checkpoints, scaffold a structured manifest to record decisions and learnings, populate fields like load_principles and pending, then commit changes to enable reproducible handoffs across sessions.

What is a session checkpoint manifest and when do I need one?▼

A session checkpoint manifest is a structured record that captures decisions and learnings from a work session. You need one when ending sessions to create a reproducible reference for the next session or teammates.

How do I surface and triage drift observations before committing a session?▼

To surface and triage drift observations before committing, use the drift gate feature to review drift_observed fields in the manifest, ensuring learnings are evaluated before the final session commit.

Do I need git to create a session checkpoint manifest?▼

Git is used to back the checkpoint manifest and store learnings through commit-session workflows. The commit sequence relies on git to store changes and support reproducible memory retention across sessions.

What's the best way to structure a session handoff for memory retention?▼

The best way to structure a session handoff is to populate a standard manifest format with load_memory_refs, pending tasks, and completed items, then ingest learnings and execute the commit-session sequence.

Why does my session checkpoint workflow not retain memory across handoffs?▼

Session checkpoint memory retention fails when learnings are not ingested via ingester_ingest calls or when the commit sequence is incomplete. Ensure you execute both commit-session and session-end commands.