cc-history

Analyze Claude Code JSONL logs for token usage and tool invocations.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sachio222/based-stack --skill cc-history-sachio222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-history
Source: https://github.com/sachio222/based-stack/tree/main/cc-history
Command: npx skills add https://github.com/sachio222/based-stack --skill cc-history-sachio222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code History Analysis documentation provides structured guidance for querying and analyzing Claude Code conversation history files stored as JSONL logs, enabling quick extraction of patterns, usage metrics, and tool invocations.

Core Features & Use Cases

  • Reference patterns for locating and interpreting Claude Code history data.
  • Instructions for extracting token usage, subagent interactions, and tool invocations from JSONL logs.
  • Use Case: Investigating large conversations to identify growth points and optimize history review workflows.

Quick Start

Query the latest Claude Code history JSONL to summarize token usage and subagent interactions in one pass.

Frequently Asked Questions about cc-history

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

FAQPage Schema
How do I analyze Claude Code conversation history stored in JSONL logs?

Analyzing Claude Code conversation history in JSONL logs involves parsing message structures, types, and usage fields to extract token usage metrics, subagent interactions, and tool invocations across sessions.

What is the best way to audit token usage in Claude Code sessions?

Auditing token usage in Claude Code sessions is best done by querying JSONL history files to summarize token consumption and subagent interactions in a single pass for optimizing review workflows.

Can I extract subagent interactions and tool invocations from Claude Code history files?

Extracting subagent interactions and tool invocations from Claude Code history files is supported by applying query patterns to parse JSONL logs for correlations and branch exploration.

How do I diagnose efficiency and growth points in large Claude Code conversations?

Diagnosing efficiency and growth points in large Claude Code conversations requires investigating JSONL history logs to identify usage patterns, token consumption, and subagent interactions across active sessions.

What query patterns work for locating file structure and branch exploration in Claude Code history?

Query patterns for file structure and branch exploration in Claude Code history leverage JSONL parsing to map subagent correlations and trace session messages, types, and usage fields.

Do I need any dependencies to parse JSONL logs for Claude Code history analysis?

Parsing JSONL logs for Claude Code history analysis requires no external dependencies, as the process applies structured query guidance directly to the stored conversation files to extract insights.