file-archaeology

Investigate Git file origins and change history into a Markdown report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/swat9013/dotfiles --skill file-archaeology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-archaeology
Source: https://github.com/swat9013/dotfiles/tree/main/.claude-global/skills/file-archaeology
Command: npx skills add https://github.com/swat9013/dotfiles --skill file-archaeology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically uncovers why a file exists, who changed it, and how its design evolved so maintainers can make informed decisions about fixes, refactors, or removals.

Core Features & Use Cases

  • Chronological provenance: Gather full change history including renames and merge points to identify initial introduction and major rewrites.
  • Targeted investigations: Use pickaxe and regex searches, blame, and bisect guidance to locate when specific strings or behaviors were added or removed.
  • Reproducible reporting: Compile findings, evidence, and executed git commands into a Markdown report suitable for code reviews, incident postmortems, or design documentation.
  • Use Case: Trace why a CI script was added, identify the merge request that introduced a flaky job, and produce an evidence-backed remediation plan.

Quick Start

Run file-archaeology on the target filepath to produce a dated Markdown report summarizing introduction, key changes, and unresolved questions.

Frequently Asked Questions about file-archaeology

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

FAQPage Schema
How do I investigate git history to find why a file was added or changed?

Git history investigation extracts full change logs, blame data, and merge commits to trace file origins and design intent. It uses pickaxe searches and chronological provenance to identify initial introduction and major rewrites for maintainers.

What is the best way to trace when a specific string or behavior was introduced in a git repository?

Tracing specific strings in git relies on pickaxe and regex searches to locate exact commits where content was added or removed. Blame analysis and bisect guidance further pinpoint regression root-causes across branches and merge points.

Can I analyze file provenance across multiple branches and merge commits?

Yes, file provenance analysis works across branches and merge commits to reconstruct design intent and identify regression root-causes. It gathers chronological change history including renames and merge points to ensure comprehensive evidence-backed findings.

How do I generate a reproducible report of git forensics and code history findings?

Git forensics reporting compiles findings, evidence, and executed git commands into a dated Markdown report. This reproducible output is suitable for code reviews, incident postmortems, or design documentation, ensuring all provenance analysis is traceable.

Does git bisect guidance work for finding the root cause of regressions in file history?

Git bisect guidance helps locate regression root-causes by analyzing file history and targeted changes. Combined with blame and pickaxe searches, it narrows down the specific commits that introduced flaky jobs or behavioral shifts for evidence-backed remediation.