danyuchn

History Find — AI skill for Claude Code

AI community

Find a past Claude Code or Codex conversation from a vague memory — no exact keywords needed.

How to install History Find

This entry records only its repository, not the path inside it, so there is no exact command to give. Open danyuchn/history-find and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What History Find does

Find a past Claude Code or Codex conversation from a vague memory — no exact keywords needed. 用模糊的印象找回過去的 AI 對話。

Alternatives in AI

  • Vibeproxy — Native macOS menu bar app to use your Claude Code & ChatGPT subscriptions with AI coding tools - no API keys n 3.3k ★
  • Deepseek Pp — DeepSeek Web browser extension: AI agent workspace with MCP tools, memory, Skills, automation, web search, and 1.7k ★
  • Paritok 4b V1 — Non-destructive compression gateway for AI coding agents 1.4k ★

README

history-find

**English** · [中文](README.zh-TW.md)

A [Claude Code](https://claude.com/claude-code) skill that finds a past Claude Code or Codex conversation from a vague memory — when you remember *what you did* but not the words you used.

The problem

You remember designing something months ago — a batch import, a refactor plan, a pricing model — but you can't remember the exact wording you used, so keyword search finds nothing. Meanwhile the work is spread across a parent session, two forks, and a subagent transcript.

What it does

Instead of trusting one search tool, it works in layers:

fuzzy memory
    -> metadata narrowing        (dates, projects, titles, paths)
    -> content search            (actual prompts and replies)
    -> model reranking           (task, artifacts, actions, sequence)
    -> chain reconstruction      (parent + forks + subagents as one piece of work)
    -> 1-5 evidence-backed candidates

It returns a ranked shortlist with a confidence label, the evidence behind each match, and the exact session paths — plus an explicit list of what it *did not* check, so a miss is never reported as "doesn't exist".

What makes it different

  • Keeps evidence layers separate. Metadata proving a session exists is not the same as message content proving what was discussed. A model-generated title is a clue, not proof.
  • Never reports a false zero. An empty full-text table means "this index is empty", not "your history is empty" — the skill says so and keeps looking.
  • Reconstructs work chains. One task often spans a parent session and its forks. It returns the parent where your decisions live, not just the child that happened to match a keyword.
  • Read-only by default. It does not resume, rename, export, or delete anything, and it does not send transcript content to external services.

Requirements

Works with whatever you have; it degrades instead of failing: