history-insight

Extract actionable insights from Claude Code JSONL session histories.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Driving-Teacher/driving-teacher-ai-native --skill history-insight-driving-teacher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: history-insight
Source: https://github.com/Driving-Teacher/driving-teacher-ai-native/tree/main/.claude/skills/history-insight
Command: npx skills add https://github.com/Driving-Teacher/driving-teacher-ai-native --skill history-insight-driving-teacher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps users access, capture, and reference Claude Code session history for saving, extracting, summarizing, or reviewing.

Core Features & Use Cases

  • Extracts user and assistant messages from Claude Code session logs (JSONL) and produces a concise history summary.
  • Generates actionable insights, trends, and decisions from past conversations for audits or knowledge retention.
  • Use Case: When preparing for a project, summarize prior sessions to align next steps and decisions.

Quick Start

Capture the current Claude Code session history and generate a concise insights report.

Frequently Asked Questions about history-insight

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

FAQPage Schema
How do I extract insights from Claude Code session history?

Extract insights from Claude Code session history by parsing JSONL session files to summarize user and assistant messages, generating actionable trends and decisions for audits or knowledge retention across current or multiple projects.

What is the best way to summarize past Claude Code conversations for project preparation?

Summarize past Claude Code conversations by analyzing JSONL session logs to produce concise history summaries, aligning next steps and extracting prior decisions for project preparation and knowledge retention.

Does this session history analysis tool require jq to parse JSONL files?

Yes, parsing JSONL session files requires jq as a dependency to extract user and assistant messages from Claude Code logs and generate structured insights suitable for dashboards or reports.

Can I review session histories across multiple projects using Claude Code logs?

Review session histories across multiple projects by accessing JSONL files located under ~/.claude/projects/<encoded-cwd>, extracting and summarizing past conversations to generate actionable insights for each project context.

What structured output formats can I generate from Claude Code session data?

Generate structured insights suitable for dashboards or reports from Claude Code session data, transforming JSONL logs into concise summaries, trends, and decisions extracted from user and assistant messages.

Why am I unable to find my Claude Code conversations in the session logs?

Claude Code conversations are stored as JSONL session files under ~/.claude/projects/<encoded-cwd>, using encoded working directory paths; ensure you are searching the correct encoded project path to locate and extract session history.