Git Archaeology

Name: Git Archaeology
Availability: InStock
Author: strategicmilk

Trace git history to uncover design decisions and regressions.

Updated Mar 3, 2026

Search Tags:#git #debugging #analysis #provenance #bisect #code-history

Ready to run

npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill git-archaeology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Git Archaeology
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/worker/git-archaeology
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill git-archaeology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often need to understand why a piece of code was written in its current form, especially when encountering complex workarounds, regressions, or undocumented decisions. This skill reveals the underlying version‑control history to provide that context.

Core Features & Use Cases

Blame & Log Analysis: Identify the commits that introduced each line or function and extract their messages.
Bisect Assistance: Narrow down regressions by automatically running git bisect when good/bad commits are supplied.
Timeline Synthesis: Produce a chronological narrative of significant changes, highlighting design decisions and their motivations.
Provenance Reporting: Return a structured JSON report with timelines, key findings, and safety recommendations for further modifications.

Quick Start

Ask the Git Archaeology skill to trace the history of a function and receive a concise report of its evolution.

Frequently Asked Questions about Git Archaeology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace git history to find out why a piece of code was written?▼

Trace git history by applying blame and log analysis to files or symbols. This reveals the commits that introduced specific lines and extracts their messages to explain the original design decisions and motivations.

Can I use git bisect to narrow down regressions automatically?▼

Yes, git bisect can narrow down regressions automatically. You need to supply known good and bad commits, and the skill runs the bisect operations to identify the exact commit that introduced the regression.

What is the best way to investigate code provenance for a specific date range?▼

Investigate code provenance by applying history tracing to a specific date or commit range. This synthesizes a chronological timeline of significant changes, highlighting design decisions and their underlying motivations.

Does git blame analysis work on individual functions or only entire files?▼

Git blame analysis works on both individual functions and entire files. You can apply the skill to specific symbols, files, or commit ranges to identify which commits introduced each line and extract their messages.

How do I get a structured report of code history changes and safety recommendations?▼

Get a structured report of code history by running timeline synthesis and provenance analysis. This returns a structured JSON report containing chronological timelines, key findings, and safety recommendations for further modifications.