session-chapter

Checkpoint layered chapter state before Claude Code context compression.

1|Updated May 17, 2026
One-click install
npx skills add https://github.com/mykcs/myk-skills --skill session-chapter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-chapter
Source: https://github.com/mykcs/myk-skills/tree/main/session-chapter
Command: npx skills add https://github.com/mykcs/myk-skills --skill session-chapter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents long Claude Code sessions from losing progress by capturing layered “chapter” state (task, next steps, decisions, and blockers) before context compression, then enabling seamless restoration in a new window with clean context.

Core Features & Use Cases

  • Chapter checkpointing: Diagnoses context pressure, captures task stage, artifacts, and token usage into structured files under .omc/chapters/.
  • Decision event sourcing: Appends an immutable decisions.md log to preserve the full reasoning chain across windows.
  • Priority Context restoration: Writes the current chapter summary into Priority Context via /notepad_write_priority so SessionStart can auto-inject it on new windows.
  • Compression strategy selection: Chooses between /rewind (targeted summarization), /compact with a custom instruction, or skipping compression when context is already extremely high.
  • Recovery pathways: Supports restoring via a clean new window (recommended), a structured /chapter_resume flow from chapter files, or a fallback claude --resume UUID flow.

Quick Start

When you notice the context is getting full or you want to pause and continue in a new window, run the session-chapter workflow and then start a clean new window via cd [project path] && claude to get automatic Priority Context injection.

Frequently Asked Questions about session-chapter

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

FAQPage Schema
How do I preserve Claude Code session progress before context compression?▼

Preserving Claude Code session progress before context compression involves checkpointing layered chapter state into structured files under .omc/chapters, capturing task stage, artifacts, and token usage to enable seamless restoration in a new window.

What is the best way to resume a long-running coding task in a new Claude Code window?▼

The best way to resume a long-running coding task is to start a clean new window using the cd [project path] && claude command, which triggers automatic injection of the Priority Context summary saved during the previous checkpointing process.

How does decision logging work for multi-stage refactoring tasks across context windows?▼

Decision logging for multi-stage refactoring tasks works by appending an immutable decisions.md log that preserves the full reasoning chain, ensuring event sourcing tracks every decision made across different Claude Code windows.

When should I choose /rewind over /compact for context compression?▼

You should choose /rewind over /compact for context compression when you need targeted summarization of specific sections, whereas /compact applies broader custom instructions, or you can skip compression entirely if context pressure is already extremely high.

Does session checkpointing support recovery if I accidentally close my Claude Code terminal?▼

Session checkpointing supports terminal closure recovery through structured /chapter_resume flows from chapter files, or alternatively via a fallback claude --resume UUID flow if the session identifier is still accessible.