chat-compactor

Generate structured markdown session summaries and save them to .handoff files.

Updated May 26, 2026
One-click install
npx skills add https://github.com/XWIlluDelu/agent-share --skill chat-compactor-xwilludelu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chat-compactor
Source: https://github.com/XWIlluDelu/agent-share/tree/main/lib/chat-compactor
Command: npx skills add https://github.com/XWIlluDelu/agent-share --skill chat-compactor-xwilludelu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents lost continuity by turning messy chat history into structured, machine-readable summaries that help the next AI session pick up exactly where the last one left off.

Core Features & Use Cases

  • Session compaction for continuity: Creates a scannable handoff document that captures outcomes, decisions, rationale, and blockers so the next agent does not re-derive context.
  • Dead-end documentation: Records approaches that failed so they are not retried, reducing wasted cycles.
  • Prioritized next steps: Produces an actionable, ordered checklist to guide immediate follow-through after a task switch or break.
  • Use case: After a debugging or implementation sprint, compact the session to preserve what worked, what broke, which files changed, and what should happen next for the same project.

Quick Start

Ask your AI agent: “Compact and summarize this session, and save the handoff so the next session can continue without re-explaining.”

Frequently Asked Questions about chat-compactor

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

FAQPage Schema
How do I create a session handoff summary for AI continuity?

To create a session handoff summary, compact your chat history into structured markdown documenting decisions, outcomes, and next steps. This preserves context so the next AI agent can continue coding or debugging without re-explaining the background.

What is context compaction and when do I need it for debugging?

Context compaction summarizes a long chat history into a machine-readable format. You need it when the context window gets long during a debugging sprint, ensuring continuity and preventing lost decisions before ending an AI session.

How do I document failed approaches to prevent dead-ends in future AI sessions?

Document failed approaches by generating a session summary that explicitly records dead-ends and blockers. This prevents the next AI agent from re-deriving context or retrying methods that already failed, saving debugging cycles.

Can I save a structured markdown handoff file directly to my project directory?

Yes, you can save a structured markdown handoff file directly to your project. The summary is automatically saved to a .handoff/session-[topic]-[date].md file, creating a scannable document for later agent retrieval.

What is the best way to prepare an actionable checklist for the next coding session?

The best way to prepare an actionable checklist is to compact the session into a prioritized list of next steps. This ordered checklist guides immediate follow-through after a task switch, capturing what worked and what should happen next.

Does session summarization work without additional dependencies or components?

Yes, session summarization works without additional dependencies. The compaction process relies solely on your existing AI agent to process the chat history and output the structured markdown file directly into your project directory.