skills.rest
Xueheng-Li
Xueheng-LiCOMMUNITY
Explore all skills by this author →
GitHub

chat-history-summarizer

Extract and summarize Claude Code chat histories into structured Markdown reports.

54|19|Updated Jan 13, 2026
Search Tags:#summarization#documentation#markdown#claude#export#chat-history#conversation-logs
One-click install
npx skills add https://github.com/Xueheng-Li/sysu-awesome-cc --skill chat-history-summarizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chat-history-summarizer
Source: https://github.com/Xueheng-Li/sysu-awesome-cc/tree/main/skills/chat-history-summarizer
Command: npx skills add https://github.com/Xueheng-Li/sysu-awesome-cc --skill chat-history-summarizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool extracts and summarizes Claude Code chat history into a clear, structured documentation format, enabling easy review, handoffs, and knowledge transfer.

Core Features & Use Cases

  • Chat history extraction: Identify prompts, Claude actions, and tool usage from conversation logs.
  • Structured documentation: Generate a reusable summary with sections for metadata, rounds, and outcomes.
  • Use Case: When exporting a session, create a durable record of what happened, how decisions were made, and what tools were used.

Quick Start

Run the export workflow on a Claude Code session to produce a summarized Markdown report for archiving.

Frequently Asked Questions about chat-history-summarizer

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

FAQPage Schema
How do I export Claude Code chat history into structured Markdown documentation?▼

Exporting Claude Code chat history into Markdown documentation requires parsing raw conversation logs, identifying user prompts and Claude actions, and generating a standardized report with metadata, rounds, and outcomes.

What is the best way to summarize conversation logs for project handoffs?▼

Summarizing conversation logs for handoffs involves extracting chat history, identifying tool usage and decisions across multiple rounds, and generating a concise, structured documentation format for knowledge transfer.

Can I extract specific tool usage and Claude actions from multiple rounds of a session log?▼

Extracting specific tool usage and Claude actions from session logs is possible by parsing raw conversation data, identifying Claude markers, and structuring the extracted information into a reusable summary report.

Does this chat history summarization approach work without external dependencies?▼

The chat history summarization workflow operates without external dependencies, parsing raw logs directly to identify user and Claude markers and generate a standardized Markdown report.

When do I need to convert chat logs into a structured documentation format?▼

Converting chat logs into a structured documentation format is needed when archiving a session, creating a durable record of decisions and tool usage, or preparing conversation history for team handoffs.

What limitations exist when parsing raw conversation logs for export?▼

Parsing raw conversation logs for export requires clear identification of user and Claude markers to generate a standardized report; sessions with ambiguous markers or unstructured logs may limit extraction accuracy.

Related Skills

Explore More Content & Communication Skills→
Ar9avAr9av
3.2k

claude-history-ingest

Ingest Claude conversation histories into Obsidian wiki pages organized by project context.

Community
Advanced
kirvinkirvin

session-close

Save session state to issue notes, push work to repositories, and generate handoff instructions.

Community
Intermediate
TrreeTrree

session-summary

Generate structured Chinese session summaries saved to .claude/summaries.

Community
Advanced
mvallimmvallim
7

generate-markdown-docs

Generate Markdown documentation from codebases with customizable headings and dependencies.

Community
Intermediate