Git History Forensics Brief
Trace git history, regressions, reverts, and code ownership from supplied logs and diffs.
Free
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
OpenClaw+21 moreClaude CodeCursorCodex CLIMuseOpenClaw
Manus
Grok
Grok Bot+18 agentsGit History Forensics Brief
Example session with this skill installed
I found a regression in auth.js line 45. Here is the git blame plus the relevant git log and diffs. Build an evidence-led timeline, separate facts from hypotheses, and give me a safe verification plan.
- Read your context and instructions
- Compiled the git history forensics
- Generated the document
Executive answer
The supplied excerpts show a guard clause was removed during a session-handling refactor, followed by a partial fix. This is an illustrative example using sample evidence; verify every conclusion against the complete repository history.
Confidence: medium because the supplied diff is incomplete.
Evidence timeline
| Date | Commit | Evidence | Interpretation |
|---|---|---|---|
| 2024-02-01 | COMMIT_A | auth.js:45 changes in supplied diff | Session check was narrowed during the refactor. |
| 2024-02-04 | COMMIT_B | Follow-up patch changes the same block | A related failure was addressed, but the original guard is not shown as restored. |
Change chain
- Session-handling refactor → follow-up fix in the same module.
- Files in scope:
auth.jsand the supplied test excerpt. - No claim is made about commits or lines not included in the supplied evidence.
Findings
- Observed / high confidence: The supplied diff removes a check before reading session state.
- Observed / high confidence: The follow-up patch touches the same path.
Inferred / medium confidence: Guest or partially initialized sessions may still reach the path; confirm with runtime evidence.
- Unknown: Complete parent history, merge context, and CI results were not supplied.
Verification plan
- Run
git show COMMIT_A -- auth.jsand compare the parent revision. - Use
git log -L 45,45:auth.jsto trace the line through follow-ups. - Add or run a regression test for an uninitialized/guest session.
- Review the complete merge diff before changing production code.
Next step: provide the complete relevant history and test output for a higher-confidence conclusion. This report never invents commit hashes, blame, or test results.
git-history-forensics-brief.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Struggling to understand why a specific line of code exists or how a regression crept into a complex merge? This skill reconstructs the technical narrative of your codebase by analyzing supplied git history to trace intent, recover lost changes, and explain commit sequences.
What it does
- Trace Evolution maps the history of specific functions or files through commits and authors to find original intent.
- Recover Reverts identifies the original changes behind later reverts or follow-up patches to restore lost context.
- Causality Analysis connects specific code changes to observed symptoms or bugs based on diffs and commit messages.
- Timeline Construction organizes noisy logs into a chronological sequence of merges, fixes, and feature additions.
- Maintenance Briefs converts raw git output into actionable handoff notes for other engineers.
How it works
- Supply the specific question you are investigating along with snippets of
git log,git show, orgit blameoutput. - The agent bounds the evidence by listing supplied commits and identifying gaps in the history provided.
- It builds a causal timeline, distinguishing between facts found in the diffs and hypotheses about the logic.
- You receive a structured report including an evidence timeline, change chain, and a low-risk verification plan.
Frameworks & tools
This tool is language-agnostic and works with any repository using Git. It processes standard output from command-line git tools, patches, and diff files.
Why this beats prompting it yourself
Generic LLMs often hallucinate commit hashes or misinterpret complex merge conflicts. This skill follows a strict archaeological method that separates observed facts from inferences, ensuring you never act on "hallucinated" code history.
Use cases
- Investigating the root cause of a regression by tracing back through a series of merges.
- Auditing a risky subsystem before refactoring to understand existing side effects.
- Drafting a technical handoff for a new maintainer who needs to understand "why" a fix was applied.
- Recovering the logic from a feature that was reverted months ago.
Known limitations
Does not have live repository access. You must provide the logs, blames, or diffs manually. It cannot detect behavior not reflected in the provided text snippets.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean today
- Free to download with an account