- Home
- Skills
- Testing & Debugging
- Git History Archaeologist
Works with the AI Agents you already use
Git History Archaeologist
Excavate git history: blame forensics, reverted-change recovery, and commit narrative reconstruction.
$5
Git History Archaeologist
Example session with this skill installed
Why does the authentication logic in auth.ts look like this? It seems to have changed recently and is causing intermittent timeouts.
- Read your context and instructions
- Compiled the git history archaeologist
History: auth.ts
Timeline
| Commit | Date | What changed | Why (deduced) |
| 8a2f3c | 2023-10-12 | Added retry logic | Handle flaking LDAP |
| 4d1b9e | 2023-11-05 | Async wrapper | Fix race condition |
Answer
Timeouts were introduced in 4d1b9e. Evidence: sha 4d1b9e.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Standard git blame often points to a formatter or a minor refactor rather than the original intent. Developers struggle to reconstruct the "why" behind legacy code or pinpoint exactly when a regression was introduced across a deep commit history.
What it does
- Performs forensic analysis of git logs to trace the evolution of specific files or behaviors.
- Triangulates regressions using automated git bisect workflows and test suite execution.
- Identifies the original intent of changes by following renames and searching for specific string introductions.
- Produces chronological timelines that summarize code evolution from birth to its current state.
- Generates evidence-backed action plans for reverting or maintaining specific logic.
Why this beats prompting it yourself
Manually running git log and bisect is tedious and error-prone. This skill automates the triangulation process, correctly handles file renames that break standard tools, and deduces developer intent from diff patterns when commit messages are sparse.
Use cases
- Identify the specific commit that broke a feature and determine a revert strategy.
- Onboard to a complex legacy module by generating a timeline of its major architectural shifts.
- Audit code changes to find the original PR or issue reference for a specific line of code.
- Prepare detailed release notes by reconstructing the narrative of changes over a specific range.
Large logs are paginated and scoped to prevent context overflow. Does not replace live debugging of blockers but orchestrates the search for the root cause in history.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
This skill has been used 89 times.
Trust & safety
Security scan
Security scan passed 3 months ago
Requires