Investigating Repository History

Reconstructs cited git/PR history before risky edits, with confidence-scored evidence.

Tested · Works

Test report

Verdict
Tested · Works
Score
9.6/10
Tested
Jul 14, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · 4fec75b

Ran it against a real renamed-and-refactored Go safety-hook file: blame correctly traced content through a directory rename and showed the exact function hadn't been touched since the original consolidation commit -- a genuinely useful, cited answer a quick eyeball-the-code pass would have missed.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 5/5
  • Triggers reliably 5/5
  • Output vs. baseline 9/10
  • Docs & honesty 5/5

What Investigating Repository History does

Uses git blame/log plus GitHub PR and review-comment evidence to explain why code exists before you touch it, flagging squash/rebase/rename traps and rating evidence confidence (high/medium/low, never invented). Triggers before edits to API, security, concurrency, persistence, or migration-sensitive code, or when asking which PR introduced a behavior or whether a change is safe.

How to install Investigating Repository History

git clone https://github.com/CodeAlive-AI/ai-driven-development
cd ai-driven-development
mkdir -p ~/.claude/skills
cp -r skills/investigating-repository-history ~/.claude/skills/investigating-repository-history

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Investigating Repository History

  • /investigating-repository-history Reconstructs cited git/PR history before risky edits, with confidence-scored evidence.

It also activates on plain-language prompts like these:

  • Before I touch this auth code, find out why it was written this way
  • Dig up the PR history behind this concurrency fix before I change it
  • Explain why this migration exists before I refactor it further

Frequently asked questions

Is the Investigating Repository History skill free?
Yes. The skill itself is free from CodeAlive-AI/ai-driven-development. SkillProof publishes the install command and an independent test verdict at no cost.
Does Investigating Repository History work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 14, 2026. Verdict: Tested · Works. Ran it against a real renamed-and-refactored Go safety-hook file: blame correctly traced content through a directory rename and showed the exact function hadn't been touched since the original consolidation commit -- a genuinely useful, cited answer a quick eyeball-the-code pass would have missed.
What is the Investigating Repository History SkillProof Score?
9.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 9/10, docs & honesty 5/5.
How do I install Investigating Repository History?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Investigating Repository History with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.