claude-code-history-files-finder

Recover deleted code from Claude Code session history files.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/HuuBar/skill-routing-experiment --skill claude-code-history-files-finder-huubar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-history-files-finder
Source: https://github.com/HuuBar/skill-routing-experiment/tree/main/unified_skills/daymade/claude-code-history-files-finder
Command: npx skills add https://github.com/HuuBar/skill-routing-experiment --skill claude-code-history-files-finder-huubar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Claude Code stores project sessions and content; this skill helps developers locate, recover, and analyze past work from session histories to reconstruct deleted files, trace changes, and extract useful code.

Core Features & Use Cases

  • Recover deleted or modified code from Claude Code session history files
  • Search sessions for keywords across a project and rank results by relevance
  • Analyze tool usage and file operations to understand how code evolved over time
  • Produce a detailed recovery report and preserve original directory structure for inspected files

Quick Start

Use the scripts to list sessions, search for keywords, and recover content from session history to a local folder.

Frequently Asked Questions about claude-code-history-files-finder

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

FAQPage Schema
How do I recover deleted code from Claude Code session history files?

You can recover deleted code from Claude Code session history by using scripts to locate past sessions by project, search keywords across JSONL data, and extract Write tool outputs to reconstruct lost files.

Can I search for specific keywords across past Claude Code sessions?

Yes, you can search for specific keywords across past Claude Code sessions. The skill filters session history JSONL files and ranks results by relevance to help you locate exact code changes.

What is the best way to analyze file changes over time from session history?

Analyzing file changes over time from session history involves streaming JSONL processing and deduplication of file writes to trace code evolution and produce a detailed recovery report.

Does this session history recovery approach require any external dependencies?

No, this session history recovery approach requires no external dependencies. It operates independently using internal scripts and references to process JSONL files and generate recovery reports.

How do I generate a recovery report for reconstructed code?

To generate a recovery report for reconstructed code, run the provided scripts to analyze tool usage and file operations, which outputs a detailed summary while preserving the original directory structure.