dig
Skill121 starsChanged 7 months agoMITView on GitHub
Mine Claude Code sessions — timeline, gaps, repo attribution, session history. Use when user says "dig", "sessions", "past sessions", "timeline", "what did I work on", or wants to see session history. Do NOT trigger for finding code/projects (use /trace), exploring repos (use /learn), or current session status (use /recap).
6 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- uwonu606/claude-skillstheir own version, first seen Nov 1, 2026
- WeAIClub/resume-skillstheir own version, first seen Oct 25, 2026
- l3rowniecakez/Claude_Skilledited, first seen Oct 19, 2026
- apify/apify-mcp-servertheir own version, first seen Aug 10, 2026
- tim-mcdonnell/skillstheir own version, first seen Jul 29, 2026
- rioX432/agent-witnesstheir own version, first seen Jul 2, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- l3rowniecakez/Claude_Skill★ 097% same
Wrote their own version · 5
- apify/apify-mcp-server★ 15ksame name
- WeAIClub/resume-skills★ 4same name
- rioX432/agent-witness★ 1same name
- tim-mcdonnell/skills★ 0same name
- uwonu606/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- about-oracleSkill
- awakenSkill
- bampenpienSkill
- budSkill
- create-shortcutSkill
- feelSkill
- forwardSkill
- goSkill
- incubateSkill
- learnSkill
- oracle-cheatsheetSkill
- oracle-family-scanSkill
- oracle-prismSkill
- philosophySkill
- projectSkill
- psiSkill
- recapSkill
- resonanceSkill
- round-tableSkill
- rrrSkill
- soulSkill
- traceSkill
- where-we-areSkill
- who-are-youSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 77
Run the dig script. Pass 0 for --all (no limit), or N if user specified a count, default 10:
- Very specific: line 87
When --deep is used, add extra columns to the table:
- Very specific: line 101
Read the JSON output and display as a table.
- Very specific: line 123
Repo: use repoName field from dig.py output (resolved via ghq)
- Very specific: line 132
When --timeline flag is present, group sessions by date instead of a flat table.
- Very specific: line 134
Step 1: Run dig.py with 0 for --all (scans all sessions), or user-specified count
- Distinctive: line 175
After displaying the timeline, log the discovery to Oracle so it's searchable later:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/dig - Session Goldminer v2
Mine Claude Code session data for timelines, gaps, and repo attribution. No query needed.
Usage
/dig # Current repo, 10 most recent
/dig [N] # Current repo, N most recent
/dig --all # All repos, ALL sessions (auto-detect count)
/dig --all [N] # All repos, N most recent
/dig --deep # Deep scan — ALL .jsonl files (not just most-recent per project)
/dig --deep [N] # Deep scan, N most recent
/dig --all --deep # All repos, deep scan — full coverage
/dig --timeline # Day-by-day grouped (current repo)
/dig --all --timeline # Day-by-day grouped (all repos, ALL sessions)Deep Mode (#216)
Standard /dig deduplicates by session basename — only showing the most recent file per session. This misses historical sessions, subagent sessions, and worktree sessions.
--deep scans ALL .jsonl files across all project directories. Output includes extra fields:
toolCalls— number of tool invocations in the sessionfileSizeKB— session file size in KB- Coverage metadata:
"X of Y sessions"showing how many were returned vs found
Timezone (#214)
dig.py v2 auto-detects timezone instead of hardcoding GMT+7:
MAW_DISPLAY_TZenv var (e.g.,Asia/Bangkok,7,America/New_York)TZenv var- System timezone
- Fallback: UTC
Output metadata includes detected timezone name and offset.
Step 0: Timestamp
date "+🕐 %H:%M %Z (%A %d %B %Y)"
ENCODED_PWD=$(pwd | sed 's|^/|-|; s|[/.]|-|g')
PROJECT_BASE=$(ls -d "$HOME/.claude/projects/${ENCODED_PWD}" 2>/dev/null | head -1)
export PROJECT_DIRS="$PROJECT_BASE"
# Strip -wt* suffix to find parent project dir
PARENT_ENCODED=$(echo "$ENCODED_PWD" | sed 's/-wt-[^/]*$//')
if [ "$PARENT_ENCODED" != "$ENCODED_PWD" ]; then
PARENT_BASE=$(ls -d "$HOME/.claude/projects/${PARENT_ENCODED}" 2>/dev/null | head -1)
[ -n "$PARENT_BASE" ] && export PROJECT_DIRS="$PROJECT_DIRS:$PARENT_BASE"
fi
# nullglob-safe worktree scan (both parent and self)
for base in "$PROJECT_BASE" "$PARENT_BASE"; do
[ -z "$base" ] && continue
for wt in "$base"-wt-*(N); do # (N) = zsh nullglob qualifier
[ -d "$wt" ] && export PROJECT_DIRS="$PROJECT_DIRS:$wt"
done
doneEncodes pwd the same way Claude does (replace / and . with -, prepend -) to match the .claude/projects/ directory naming (e.g. github.com → github-com). Detects parent project from worktree dirs (strips -wt-* suffix) and includes both parent and self worktrees. The (N) qualifier prevents zsh crashes when no worktrees exist.
With --all (all repos):
export PROJECT_DIRS=$(ls -d "$HOME/.claude/projects/"*/ | tr '\n' ':')Step 2: Extract Session Data
Run the dig script. Pass 0 for --all (no limit), or N if user specified a count, default 10:
python3 ~/.claude/skills/dig/scripts/dig.py [N] [--deep]
# N=10 (default), N=0 (scan all sessions), N=50 (50 most recent)
# --deep: scan ALL .jsonl files (not just most-recent per basename)Deep Mode Display
When --deep is used, add extra columns to the table:
| # | Date | Session | Min | Repo | Msgs | Tools | Size | Focus |And show coverage in the footer:
**Coverage**: [returned]/[found] sessions | **Timezone**: [tz_name] (GMT+[offset])Step 3: Display Timeline
Read the JSON output and display as a table. Sessions are chronological (oldest first). Gap rows (type: "gap") span the session column with · · · prefix:
## Session Timeline
| # | Date | Session | Min | Repo | Msgs | Focus |
|---|------|---------|-----|------|------|-------|
| | | · · · sleeping / offline | | | | |
| 1 | 02-21 | 08:40–09:08 | 28m | oracle-skills-cli | 5 | Wire /rrr to read pulse data |
| | | · · · 45m gap | | | | |
| 2 | 02-21 | 09:55–10:23 | 28m | homelab | 3 | oracle-pulse birth + CLI flag |
| | | · · · no session yet | | | | |
**Dirs scanned**: [list PROJECT_DIRS]
**Total sessions found**: [count]Column rendering rules:
- Gap rows:
| | | · · · [label] | | | | |— number + date empty, label in Session col - Date:
MM-DDshort format (strip year) - Session:
HH:MM–HH:MMusingstartGMT7andendGMT7(strip date, keep time only) - Min:
[durationMin]m - Repo: use
repoNamefield from dig.py output (resolved via ghq) - Msgs:
realHumanMessagescount
"Msgs" = real typed human messages (not tool approvals).
With --timeline: Group by Date
When --timeline flag is present, group sessions by date instead of a flat table. Use --all to see all repos (recommended for timeline).
Step 1: Run dig.py with 0 for --all (scans all sessions), or user-specified count
Step 2: Group sessions by date from startGMT7. Render each day as:
## Feb 22 (Sun) — [vibe label]
· · · sleeping / offline
08:48–09:11 23m homelab Update Fleet Runbook + Explore black.local
09:11–11:30 139m homelab Set Up KVM OpenClaw Node on black.local
09:37–12:51 194m Nat-s-Agents /recap → supergateway → CF ZT → arra-oracle-v3 dig
· · · 45m gap
12:51–13:03 12m Nat-s-Agents Dig All + Design arra-oracle-v3 ← current
· · · no session yet
## Feb 21 (Sat) — Long day: Fleet + Brewing + Skills
06:19–08:38 139m homelab Moltworker Gateway + MBP Node
08:40 (bg) openclaw ClawHub Build Script (idle long)
09:23–16:08 405m homelab Debug MBP Node 401 — Gateway Token AuthRendering rules:
- Day header:
## MMM DD (Day) — [vibe label]— infer vibe from session summaries (e.g. "Infrastructure Day", "Brewing + Skills") - Session rows:
HH:MM–HH:MM [N]m REPO Summary— userepoNamefor repo,summaryfor focus - Gap rows:
· · · [label]between sessions when gap > 30 min - Sidechain: prefix
(bg)for sessions withisSidechain: true - Current: append
← currentmarker on the last session of the current day (today only) - Sort: days newest-first, sessions within each day oldest-first (chronological)
- Date format:
startGMT7time portion only (HH:MM),endGMT7time portion (HH:MM) - Repo width: pad repo names to align columns
Step 3: Show summary footer:
**Days**: [count] | **Sessions**: [count] | **Total time**: [sum of durationMin]mTrace Connection
After displaying the timeline, log the discovery to Oracle so it's searchable later:
arra_trace({
query: "dig session [N]",
project: "[repo-name]",
foundFiles: [],
foundCommits: [list of commit hashes from timeline],
foundIssues: []
})This connects /dig discoveries to /trace — "When did we first work on X?" becomes answerable.
ARGUMENTS: $ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

