Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

Claude Code History Files Finder

Searches every Claude Code (and optionally Codex) session archive and recovers deleted files byte-for-byte from file-history snapshots.

UtilitiesIntermediate★ 1,323⑂ 212AI score 9/10Last updated: Aug 8, 2026

What it does

A forensic search-and-recovery toolkit for the JSONL session logs Claude Code writes to disk.

  • Complete-source search: auto-discovers the default home (~/.claude), per-profile homes (~/.claude-profiles/*), the current CLAUDE_CONFIG_DIR, and every long-term archive registered in ~/.claude/history-sources.json. --all-projects sweeps everything when you don't know the project; --codex adds Codex rollouts.
  • Exact file recovery: restores the exact captured bytes from file-history snapshots — including post-Write Edit/shell changes and binary files. Without a snapshot it falls back to the latest Write call and clearly labels it as lower fidelity, and it fails loudly rather than silently substituting stale content.
  • Session analytics & triage: message/tool statistics, a verbatim "what the user actually typed" HTML report with harness noise filtered out, and a triage command that classifies how sessions ended (done, stuck_no_result, interrupted_explicit, net_error, empty).

Who it's for

  • Anyone who needs to dig a snippet or decision out of a conversation from days ago
  • Developers who deleted a file and want it back from session history
  • Users running multiple model profiles or mixing Claude Code with Codex
  • Teams auditing which sessions a crash or reboot cut off

Examples

  1. Unknown project: python3 scripts/analyze_sessions.py search --all-projects 'refactor plan' — then re-run with --exclude-session <id> because the phrase you just typed makes the current session the top hit.
  2. Recover a deleted component: locate the session via search, then python3 scripts/recover_content.py <session.jsonl> -k ImportantFile -o ./recovered_ui/ and verify the SHA-256 in recovery_report.txt.
  3. Post-crash backlog audit: python3 scripts/analyze_sessions.py triage --all-projects --kind stuck_no_result prints the full last assistant message so you can pick what to resume.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the daymade-claude-code/claude-code-history-files-finder folder from the GitHub repo daymade/claude-code-skills into my ~/.claude/skills/claude-code-history-files-finder/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/daymade/claude-code-skills.git /tmp/daymade-skills && mkdir -p ~/.claude/skills && cp -r /tmp/daymade-skills/daymade-claude-code/claude-code-history-files-finder ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and create the skills directory: mkdir -p ~/.claude/skills
  2. Clone the repository into a temp folder: git clone https://github.com/daymade/claude-code-skills.git /tmp/daymade-skills
  3. Copy just this skill: cp -r /tmp/daymade-skills/daymade-claude-code/claude-code-history-files-finder ~/.claude/skills/
  4. Confirm Python 3 is available: python3 --version (3.9+ recommended)
  5. Restart Claude Code and ask something like "find that earlier conversation about X in my history" to trigger the skill.
  6. (Optional) If you keep older sessions in a backup location, register those roots in ~/.claude/history-sources.json so they are searched by default.
  7. Smoke-test it: python3 ~/.claude/skills/claude-code-history-files-finder/scripts/analyze_sessions.py list /absolute/path/to/project
View source on GitHub ↗License: MIT