How do I install the File History skill?

Run npx skillmds@latest add majiayu000/file-history in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is File History safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with File History?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is File History free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published File History?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

File History by majiayu000 — Agent Skill

Name: File History
Rating: 4.2 (5 reviews)
Author: majiayu000

File History

Use when looking for past work on specific FILES, understanding why code was written, or when user references "what we did before" on a file/feature. Uses file-history tracking for accurate results. PREFER THIS over episodic-memory for file-specific queries.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

File History Context

Use this for FILE-SPECIFIC history queries. For general semantic search across all conversations, use episodic-memory instead.

When to Use This Skill

USE file-history when:

Looking for sessions that edited a specific file
Understanding why code was written a certain way
User says "what did we do with [filename]"
User asks about past changes to a component/module
Refactoring and need to understand original intent
Code seems unusual and you want the backstory

DON'T use this when:

General conceptual questions across all projects → use episodic-memory
No specific file/feature in mind → use episodic-memory
Looking for patterns across unrelated conversations → use episodic-memory

How to Use

Dispatch the history-context agent:

Task tool:
  description: "Find history for [file/feature]"
  prompt: "Find context for [specific file or feature]. Focus on [decisions/implementation/rationale]."
  subagent_type: "history-context"

Example prompts:

"Find context for src/components/AuthForm.tsx"
"What sessions worked on the caching implementation?"
"Get history for the payment processing feature"

What You Get Back

The agent will return:

Summary of what was done and why
Key decisions and rationale
Implementation notes
Full session IDs (UUIDs) for reference
Session file paths for direct access

Why This Works Better Than episodic-memory for Files

Aspect	file-history	episodic-memory
Accuracy	Uses Claude's file-history tracking	Semantic search (fuzzy)
Speed	Indexed, instant	Searches full conversations
File mapping	Knows exactly which sessions edited which files	Guesses from content
Git dependency	None	None
Project scope	Per-project	Cross-project

Technical Details

Uses ~/.claude/commands/claude-history.py which:

Scans ~/.claude/file-history/ to build file→session index
Cross-references with ~/.claude/projects/ for session metadata
Reads and synthesizes conversation content
Returns structured context with full session IDs

---name: file-historydescription: Use when looking for past work on specific FILES, understanding why code was written, or when user references "what we did before" on a file/feature. Uses file-history tracking for accurate results. PREFER THIS over episodic-memory for file-specific queries.--- # File History Context **Use this for FILE-SPECIFIC history queries. For general semantic search across all conversations, use episodic-memory instead.** ## When to Use This Skill **USE file-history when:** - Looking for sessions that edited a specific file - Understanding why code was written a certain way - User says "what did we do with [filename]" - User asks about past changes to a component/module - Refactoring and need to understand original intent - Code seems unusual and you want the backstory **DON'T use this when:** - General conceptual questions across all projects → use episodic-memory - No specific file/feature in mind → use episodic-memory - Looking for patterns across unrelated conversations → use episodic-memory ## How to Use Dispatch the `history-context` agent: ``` Task tool: description: "Find history for [file/feature]" prompt: "Find context for [specific file or feature]. Focus on [decisions/implementation/rationale]." subagent_type: "history-context" ``` **Example prompts:** - "Find context for src/components/AuthForm.tsx" - "What sessions worked on the caching implementation?" - "Get history for the payment processing feature" ## What You Get Back The agent will return: - Summary of what was done and why - Key decisions and rationale - Implementation notes - **Full session IDs** (UUIDs) for reference - Session file paths for direct access ## Why This Works Better Than episodic-memory for Files | Aspect | file-history | episodic-memory | |--------|--------------|-----------------| | Accuracy | Uses Claude's file-history tracking | Semantic search (fuzzy) | | Speed | Indexed, instant | Searches full conversations | | File mapping | Knows exactly which sessions edited which files | Guesses from content | | Git dependency | None | None | | Project scope | Per-project | Cross-project | ## Technical Details Uses `~/.claude/commands/claude-history.py` which: 1. Scans `~/.claude/file-history/` to build file→session index 2. Cross-references with `~/.claude/projects/` for session metadata 3. Reads and synthesizes conversation content 4. Returns structured context with full session IDs

Frequently asked questions