Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsGit History Archaeologist Skill
Forensic Git history analysis to reconstruct code-change narratives and trace line ownership through repository evidence.
$5
Git History Archaeologist Skill
Example session with this skill installed
Investigate why the 'retry_limit' in connection_pool.py was changed from 5 to 3. I've attached the git log and blame for that file.
- Read your context and instructions
- Compiled the git history archaeologist
I have analyzed the provided git log and blame output for connection_pool.py. The investigation focuses on the reduction of the retry_limit constant.
Git History Archaeology Report
1. Investigation Question
Determine the rationale and timing for changing retry_limit from 5 to 3 in connection_pool.py.
2. Evidence Inventory
| Evidence | Commit / File | What It Shows | Confidence |
|---|---|---|---|
git blame | connection_pool.py:42 | Line currently set to 3 by commit a1b2c3d | High |
git log -p | a1b2c3d | Explicit change from 5 to 3 in the diff | High |
git log | e5f6g7h | Previous commit where value was originally 5 | High |
3. Commit Timeline
| Order | Commit | Date | Author | Change | Relationship |
|---|---|---|---|---|---|
| 1 | e5f6g7h | 2023-10-12 | dev_a | Initial pool implementation | Base state |
| 2 | a1b2c3d | 2024-01-15 | dev_b | Reduce retry ceiling | Direct change |
| 3 | b4c5d6e | 2024-01-16 | dev_c | Fix pool exhaustion bug | Follow-up |
4. Blame Forensics
The current value of 3 was introduced in a1b2c3d. Blame shows this line has not been touched since Jan 2024, despite major refactors in surrounding methods in Feb 2024.
7. Recovered Context
- Confirmed: The change occurred on 2024-01-15 in commit
a1b2c3d.
Strong Inference: The commit message "reduce retry ceiling to prevent db lock contention" suggests the change was a response to database performance issues, not a logic error.
- Uncertain: It is unclear if '3' was chosen based on load testing or as a temporary heuristic.
10. Useful Git Commands
To confirm the contention theory, run:
git log -S'retry_limit' -- connection_pool.py
git show a1b2c3d
11. Final Verdict
The value was reduced to mitigate database locking. The change is permanent and was followed by a pool exhaustion fix, suggesting the lower limit created new pressure on the pool size.
Next steps
- Check Jira/GitHub issue references mentioned in commit
a1b2c3d. - Run
git showon the follow-up commitb4c5d6eto see if pool size was increased to compensate.
Connects securely to your tools. The creator never sees your data.
About this skill
Understanding why a specific line of code exists or when a bug was actually introduced is difficult in old, complex repositories. The Git History Archaeologist acts as a forensics specialist to reconstruct code-change narratives and trace ownership through commit logs, diffs, and blame data. It eliminates guesswork by separating hard repository facts from developer intent.
What it does
- Trace line ownership by analyzing
git blameoutput to identify the origin of specific logic. - Reconstruct timelines to show the chronological sequence of changes, merges, and reverts affecting a file.
- Analyze reversions to distinguish between official
git revertcommands and manual code rollbacks. - Recover lost context by connecting commit messages, PR references, and diffs into a defensible narrative.
- Identify evidence gaps by flagging shallow clones, force-pushes, or squashed history that obscures the trail.
How it works
- Provide the agent with your investigation goal and available Git artifacts like logs, diffs, or blame outputs.
- The agent inventories the evidence and maps the relationship between commits and authors.
- It performs a "Revert Analysis" to see if changes were intentionally undone or modified by follow-up fixes.
- You receive a structured report detailing the confirmed history, likely hypotheses, and missing links.
Frameworks & tools
This skill works with any project using Git. It processes output from standard commands like git log, git show, git blame, and git diff.
Why this beats prompting it yourself
Generic LLMs often hallucinate commit history or speculate wildly about developer intent. This skill enforces a forensic workflow that treats commit hashes as immutable evidence and explicitly separates confirmed facts from inferences.
Use cases
- Root cause analysis to find exactly when a regression was introduced across multiple merges.
- Code audits to determine who authorized specific logic changes in a sensitive file.
- Legacy discovery to understand why a confusing block of code was added three years ago.
- Cleanup prep to see if a "temporary" fix was ever officially superseded by a proper feature.
Known limitations
Cannot access your local .git directory directly; you must paste the output of Git commands. It cannot recover history lost to hard resets or deleted branches if not present in the provided logs.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
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
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 13 days ago
- Passed all security checks, Safe to install
Requires
Git