dig

Extracts Claude Code session timelines and repository attribution from .jsonl files.

116|56|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill dig-soul-brews-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dig
Source: https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/main/src/skills/dig
Command: npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill dig-soul-brews-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you retrieve and visualize past Claude Code session data, showing timelines, gaps, and repository attribution without manual file digging.

Core Features & Use Cases

  • Timeline Mining: List recent or all sessions across repos with optional deep scanning.
  • Gap Identification: Highlights periods of inactivity and offline time.
  • Flexible Filters: Supports --all, --timeline, --deep, and count limits.
  • Use Case: When you wonder “what did I work on yesterday?” run dig to get a concise session table.

Quick Start

Ask the AI to execute the /dig command with any desired options to display your session history.

Frequently Asked Questions about dig

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

FAQPage Schema
How do I extract past Claude Code session timelines from .jsonl files?

To extract Claude Code session timelines, use the dig command to parse .jsonl session files, retrieving recent or full session history with repository attributions and gap identification.

How do I review recent Claude Code session history across multiple repositories?

Reviewing recent Claude Code session history across repositories requires setting the PROJECT_DIRS environment variable and running the dig command to display a concise session table with attributions.

What is the best way to identify gaps and offline periods in Claude Code session history?

Identifying gaps and offline periods in Claude Code session history is handled by the dig command's timeline mining feature, which highlights periods of inactivity across your repositories.

Does retrieving full session history require specific environment variables or flags?

Retrieving full session history requires the PROJECT_DIRS environment variable and Claude Code .jsonl session files. Apply optional flags like --all, --timeline, and --deep for comprehensive scanning.

Can I limit the number of sessions returned when analyzing Claude Code timelines?

Yes, you can limit the number of sessions returned during timeline analysis by applying count limits alongside optional flags like --all and --deep when executing the dig command.