File History Context

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/claude-skill-registry·0installs663starsProductivity & Planning

SKILL.md

Full skill instructions

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

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/majiayu000/claude-skill-registry --skill file-history

View on GitHub

skills/data/file-history/SKILL.md

More Productivity & Planning skills

View all

Productivity & Planning

brainstorming

Structured design dialogue that validates ideas before implementation begins.

295.4K 385.7K

View

Productivity & Planning

ui-ux-pro-max

Comprehensive design intelligence for web and mobile UI/UX across 10 technology stacks.

133.1K 383.9K

View

Productivity & Planning

writing-plans

Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps.

295.4K 268K

View

Productivity & Planning

using-superpowers

Introduction to the obra skills system with mandatory skill invocation rules and best practices.

295.4K 259.8K

View

Productivity & Planning

executing-plans

Execute a written implementation plan with critical review and task checkpoints.

295.4K 229.1K

View

Productivity & Planning

dispatching-parallel-agents

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K

View

Productivity & Planning

using-git-worktrees

Isolated git worktrees with smart directory selection and safety verification.

295.4K 205.2K

View

Productivity & Planning

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

179.7K 170.6K

View