dig

Consolidate Claude Code sessions across repos into a unified timeline with gaps.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/heman1033p-create/heman1033p-create.github.io --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/heman1033p-create.github.io/tree/main/.gemini/skills/dig
Command: npx skills add https://github.com/heman1033p-create/heman1033p-create.github.io --skill dig-heman1033p-create

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Mine Claude Code sessions across multiple repos into a single view, revealing timelines, gaps, and repo attribution for review and planning.

Core Features & Use Cases

  • Consolidates Claude Code session data from multiple repos into a unified timeline with gaps.
  • Attributes each session to its repository and shows per-session details like date, duration, and focus.
  • Supports day-by-day timeline grouping and quick drift detection for activity planning.

Quick Start

Use the /dig command to fetch the most recent Claude Code sessions and display the timeline with gaps and repo attribution.

Frequently Asked Questions about dig

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

FAQPage Schema
How do I consolidate Claude Code sessions from multiple repos into a single timeline?

To consolidate Claude Code sessions into a single timeline, use the /dig command to fetch current and historical project data, resolving repo names via ghq and normalizing times to GMT+7 for consistent reporting.

Can I detect timeline gaps and activity drift across Claude Code sessions?

Yes, you can detect timeline gaps and activity drift by applying day-by-day timeline grouping, which reveals per-session date, duration, repo attribution, and focus for review and planning.

Do I need ghq installed to extract Claude Code session data and attribute it to repositories?

Yes, you need ghq installed, as the Skill depends on it to resolve and attribute repository names correctly when consolidating Claude Code session data into a unified timeline.

What is the best way to normalize session times for Claude Code data extraction and reporting?

The best way to normalize session times for Claude Code data extraction is to use the /dig command, which automatically normalizes all per-session times to GMT+7 for consistent reporting.

Does timeline analysis for Claude Code sessions support historical projects?

Yes, timeline analysis supports historical projects by extracting and consolidating past Claude Code session data, displaying per-session date, duration, repo, and focus for comprehensive review.