dig

Parses .jsonl session files to produce timelines, gaps, and repository attribution.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thiansit/LuPang --skill dig-thiansit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dig
Source: https://github.com/thiansit/LuPang/tree/main/.claude/skills/dig
Command: npx skills add https://github.com/thiansit/LuPang --skill dig-thiansit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the manual effort of scanning Claude Code session logs to understand when work happened, where gaps occurred, and which repository each session belongs to, turning scattered .jsonl session files into a concise timeline.

Core Features & Use Cases

  • Automatic session discovery: Scans local Claude project directories for .jsonl session files and sessions-index.json to build a session index.
  • Timeline and gap analysis: Converts timestamps to GMT+7, computes session durations, and inserts human-friendly gap rows when idle periods exceed a threshold.
  • Repo attribution and summaries: Resolves repository names via ghq, extracts summaries and real human messages, and outputs a chronological or day-grouped view for quick retrospection.
  • Use case: Quickly answer "what did I work on recently" by showing recent sessions, highlighting long gaps, and attributing sessions to repos.

Quick Start

Run the dig skill in your project to list the 10 most recent sessions with timelines, gaps, and repository attribution.

Frequently Asked Questions about dig

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

FAQPage Schema
How do I build a timeline from Claude Code session logs?▼

Build a timeline from Claude Code session logs by scanning local project directories for .jsonl files, parsing timestamps, and computing durations to produce a chronological view of recent work sessions.

Can I show gaps and idle periods in my Claude Code session history?▼

Show gaps in Claude Code session history by parsing session timestamps and inserting human-friendly gap rows when idle periods between sessions exceed a defined threshold.

How do I attribute Claude Code sessions to specific repositories?▼

Attribute Claude Code sessions to repositories by using ghq to resolve repository names from local project directories and linking each parsed session file to its corresponding repo.

Do I need ghq installed to analyze Claude Code session files?▼

Yes, ghq is a required dependency for resolving repository names and attributing parsed .jsonl session files to their corresponding local project directories.

What is the best way to summarize recent work across multiple Claude Code repositories?▼

Summarize recent work across multiple Claude Code repositories by scanning all local project directories, parsing session logs, and grouping timelines day-by-day with computed durations and repo attribution.

Can I convert Claude Code session timestamps to a specific timezone like GMT+7?▼

Convert Claude Code session timestamps to GMT+7 during the parsing process, ensuring the resulting day-by-day timelines and gap calculations reflect the correct local timezone.