dig

Extracts Claude Code session timelines, gaps, and repo attribution from local .jsonl logs.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/heman1033p-create/cv-v2-kongphop --skill dig-heman1033p-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dig
Source: https://github.com/heman1033p-create/cv-v2-kongphop/tree/main/.gemini/skills/dig
Command: npx skills add https://github.com/heman1033p-create/cv-v2-kongphop --skill dig-heman1033p-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Claude Code stores every session as scattered .jsonl files across project directories, making it hard to recall what you worked on, when, and in which repository. This Skill mines those logs to reconstruct a chronological timeline of your past sessions without any manual searching. ## Core Features & Use Cases - Session Timeline Mining: Scans Claude Code project directories (including worktrees) and lists the N most recent sessions with start/end times, duration, message counts, and summaries. - Gap Detection: Automatically inserts gap markers between sessions separated by more than 30 minutes, showing when you were offline or idle. - Repo Attribution: Resolves each session to a human-readable repository name using ghq, and supports a day-by-day grouped timeline view across all repos. - Use Case: You return Monday morning and ask "what did I work on last week" — the Skill renders a day-grouped timeline of sessions, durations, and focus summaries across every repo. ## Quick Start Ask the assistant to run /dig to show my recent Claude Code sessions as a timeline with gaps and repo names.

Frequently Asked Questions about dig

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

FAQPage Schema
How do I see my past Claude Code sessions?▼

Run the /dig command to scan the .jsonl session logs under ~/.claude/projects and display the most recent sessions as a table with times, durations, repos, and summaries. Use /dig --all to include every repository, or /dig --timeline for a day-by-day grouped view.

How to find what I worked on in Claude Code last week?▼

Use /dig --all --timeline with a large count such as 200 to group sessions by date across all repos. Each day shows session time ranges, durations, repository names, and summaries, with gap markers for idle periods over 30 minutes.

Does the session timeline include worktree sessions?▼

Yes. The discovery step matches the current repo's project directory plus any sibling directories suffixed with -wt or -wt-N, so sessions recorded in git worktrees are included and deduplicated by filename.

Why are some sessions missing from the dig output?▼

Sessions are skipped when their .jsonl file contains no parseable timestamps, and only the N most recently modified files are scanned (default 10). Increase the count argument or use --all to widen the scan across project directories.

Does digging Claude Code sessions modify any data?▼

No. The scan is read-only: it only reads .jsonl logs and sessions-index.json files, prints JSON to stdout, and writes no trace logs or files. Nothing in your session history is altered.