Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsGit History Archaeologist pro
Specialized Git forensics for tracing code evolution, detecting reverts, and reconstructing commit narratives.
$5
Git History Archaeologist pro
Example session with this skill installed
Analyze file auth_service.py from line 45 to 60. I need to know why the token validation logic changed and if the previous security check was fully removed or just moved elsewhere.
- Read your context and instructions
- Compiled the git history archaeologist
- Generated the document
The investigation reveals that the token validation logic was modified to support OAuth2 scopes, and the original security check was moved to a middleware component rather than deleted.
Git History Forensic Report
Repository Scope
auth_service.py (Lines 45-60)
Timeline
| Date | Commit | Event | Evidence | Confidence |
|---|---|---|---|---|
| 2023-10-12 | a1b2c3d | Introduction | Initial validation logic added. | High |
| 2024-01-15 | e5f6g7h | Modification | Logic changed to support Scopes. | High |
| 2024-01-15 | e5f6g7h | Refactor | Original check moved to middleware/auth.py. | Medium |
| 2024-03-02 | i9j0k1l | Current State | Current implementation with bug fix i9j0k1l. | High |
Blame Findings
| Line/Range | Blame Commit | Author | Date | Evidence | Follow-up |
|---|---|---|---|---|---|
| 45-52 | e5f6g7h | dev_alpha | 2024-01-15 | Diff shows scope check insertion. | i9j0k1l |
| 53-60 | a1b2c3d | dev_beta | 2023-10-12 | Original error handling remains. | None |
Narrative Reconstruction
The logic at line 45 was altered in e5f6g7h to introduce scope-based authorization. The previous check, which validated raw token strings, was not deleted but refactored into a shared middleware utility to prevent duplication. However, the current implementation in auth_service.py lacks the explicit null-check present in the original version, which may be the source of recent reported issues.
Next steps
- Run
git show e5f6g7h:middleware/auth.pyto verify the logic was preserved correctly. - Compare the diff of
a1b2c3dvse5f6g7hto confirm the removal of the null-pointer guard. - Check
git log -S "validate_token"to see if other files were affected by this refactor.
git-history-archaeologist-pro.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.
What you get
About this skill
The problem
Git blame is a starting point, not a complete story. Developers often struggle to understand why code changed, where a deleted function went, or whether a past bug fix was accidentally reverted during a messy merge.
What it does
- Traces line origins across renames, refactors, and complex move operations.
- Detects hidden reverts by comparing patches and commit relationships rather than just searching for keywords.
- Reconstructs chronological narratives for features or bugs to distinguish between facts and interpretations.
- Analyzes merge history to identify conflict resolutions and corrective commits.
- Audits commit messages against actual diff evidence to flag discrepancies.
Why this beats prompting it yourself
General LLMs often hallucinate commit hashes or invent author intent to satisfy a prompt. This skill enforces strict evidence-based forensics, explicitly separating facts from hypotheses and grading every finding with a confidence score.
Use cases
- Pinpointing exactly when and how a regression was introduced during a specific sprint.
- Recovering lost logic by tracing deleted code to its last known stable state.
- Performing due diligence on suspicious commits or legacy code blocks with no documentation.
Known limitations
Requires read access to Git logs, diffs, or blame data. It cannot infer author intent or deployment status without explicit repository evidence.
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
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 6 days ago
- Passed all security checks, Safe to install