Git History Forensics
Investigate and recover from Git history problems with hypothesis-driven, read-only-first methods: find when/where a bug or change was introduced (bisect, pickaxe, line-history blame), recover lost commits, branches, stashes and dropped work (reflog, fsck), and reason about what gc and expiry will delete. Use when someone asks "who/when/why did this change", "I lost my commits after reset/rebase/force-push", "find the commit that broke X", "recover a deleted branch or dropped stash", or "did this secret ever enter history". Not for everyday branching or merging (use git-workflow, git-merge-conflicts), and history rewriting or secret purges are out of scope until the user explicitly authorizes them.
Security AStatic scan found no risk patternsHow grading works ›
From the source SKILL.md
Git almost never destroys data immediately. Commits that look "lost" are usually unreachable, not deleted, and they stay recoverable until reflog expiry and garbage collection remove them. Forensics is therefore a race against expiry plus a discipline: observe first, preserve, then change anything.
What this skill does
Git History Forensics is a community-contributed Claude Code skill in the storytelling sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/git-history-forensics/ and loads when your prompt matches the skill's trigger.
When to invoke it: Use when someone asks "who/when/why did this change", "I lost my commits after reset/rebase/force-push", "find the commit that broke X", "recover a deleted branch or dropped stash", or "did this secret ever enter history". Not for everyday branching or merging (use git-workflow, git-merge-conflicts), and history rewriting or secret purges are out of scope until the user explicitly authorizes them.
Who uses this skill
The Git History Forensics Claude Code skill is built for content creators, marketers, copywriters, SEO professionals, and editorial teams. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 213,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
How to install
Free
Manual install (2 steps)
mkdir -p ~/.claude/skills/git-history-forensics
curl -L https://claudskills.com/skills/git-history-forensics/SKILL.md \
-o ~/.claude/skills/git-history-forensics/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/git-history-forensics/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/git-history-forensics/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\git-history-forensics\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Telegram
📱 Install from your phone or desktop Telegram
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
Pro
One-click install via the desktop app
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
Pro
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
Frequently asked questions
How do I install the Git History Forensics Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy
SKILL.md from the source repository to
~/.claude/skills/git-history-forensics/SKILL.md and restart Claude Code. Both flows are detailed at
claudskills.com/install/.
What does the Git History Forensics skill do?
Investigate and recover from Git history problems with hypothesis-driven, read-only-first methods: find when/where a bug or change was introduced (bisect, pickaxe, line-history blame), recover lost commits, branches, stashes and dropped work (reflog, fsck), and reason about what gc and expiry will delete. Use when someone asks "who/when/why did this change", "I lost my commits after reset/rebase/force-push", "find the commit that broke X", "recover a deleted branch or dropped stash", or "did this secret ever enter history". Not for everyday branching or merging (use git-workflow, git-merge-conflicts), and history rewriting or secret purges are out of scope until the user explicitly authorizes them.
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the Git History Forensics skill?
Use Git History Forensics when your Claude Code task falls under the Content category — specifically in the storytelling area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use Git History Forensics" or describe the task and let Claude pick). Browse related skills at
/category/content/.
What is a Claude Code skill and how does the Git History Forensics skill fit in?
A Claude Code skill is a
SKILL.md file that lives under
~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Git History Forensics is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Content category. Learn more at
/learn/what-is-a-claude-skill/.
Attribution & license
Cite this skill
If you reference this skill in a blog post, paper, or documentation, you can cite it as:
APA
MichaelWeissDEV. (2026). Git History Forensics [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/git-history-forensics/
BibTeX
@misc{git-history-forensics-2026,
author = {MichaelWeissDEV},
title = {Git History Forensics [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/git-history-forensics/}
}
Embed this skill
Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →
Badge
[](https://claudskills.com/skills/git-history-forensics/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/git-history-forensics.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/git-history-forensics.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: Git History Forensics"></iframe>
Security scan
Grade A · scanned 2026-11-01 — free static scan against the OWASP Agentic Skills Top 10.
No risk patterns were found in any of the ten OWASP-aligned categories. How grading works ›
- ✓ Prompt injection
- ✓ Data exfiltration
- ✓ Supply chain
- ✓ Reverse shell
- ✓ Credentials
- ✓ Execution
- ✓ Filesystem
- ✓ Persistence
- ✓ Obfuscation
- ✓ Network
Show this grade on your repo (click to copy):
[](https://claudskills.com/skills/git-history-forensics/#security)
More Content skills
Browse all Content skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools:
PerfectStudio ·
Ucaption ·
UTagger ·
AutoXPoster ·
TestYourSkills ·
AutomationFlows ·
Au Naturel ·
Telegram @acreatorstore