git-ai-archaeology

Analyze Git history to map AI-config file evolution and generate a markdown report.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-FlorianBruniaux-claude-code-ultimate-guide --skill git-ai-archaeology-arogyareddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-ai-archaeology
Source: https://github.com/ArogyaReddy/https-github.com-FlorianBruniaux-claude-code-ultimate-guide/tree/main/examples/skills/git-ai-archaeology
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-FlorianBruniaux-claude-code-ultimate-guide --skill git-ai-archaeology-arogyareddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams understand how AI configuration tooling evolves within a Git repository by mapping creation points, change velocity, and governance milestones.

Core Features & Use Cases

  • First-commit discovery: identify when key AI-config files first appeared.
  • Monthly evolution tracking: quantify commit velocity and track maturity milestones over time.
  • MCP and PR analysis: connect significant changes to MCP server integrations and major PRs for governance insights.
  • Output reporting: generate a single slug-based markdown report summarizing findings.

Quick Start

Run the git archaeology analysis on the target repository to generate the report.

Frequently Asked Questions about git-ai-archaeology

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

FAQPage Schema
How do I track AI-config evolution and maturity phases in a Git repository?

You can track AI-config evolution by analyzing the Git repository to identify when configuration files first appeared and monitoring monthly commit velocity. This maps maturity milestones and connects major PRs to MCP integrations.

What is Git archaeology for AI tooling configuration history?

Git archaeology for AI tooling maps the creation points, change velocity, and governance milestones of AI configuration files. It generates a markdown report summarizing how AI tooling evolved over time within the repository.

How do I analyze monthly commit velocity for AI configuration files?

Analyze monthly commit velocity by running an automated Git repository analysis that quantifies changes to AI-config files over time. This tracks historical trends and outputs a slug-based markdown report for easy sharing.

Can I connect major PRs and MCP integrations to AI tooling governance changes?

You can connect major PRs and MCP server integrations to governance changes by analyzing the repository's historical trends. This maps significant structural changes to maturity phases across your AI tooling.

Does Git repository analysis for AI-config files require external dependencies?

Git repository analysis for AI-config files operates with no external dependencies. It generates a single markdown report named with the repository slug to ensure easy archival and sharing of the maturity findings.

What is the best way to generate a historical report of AI tooling changes in Git?

The best way to generate a historical report of AI tooling changes is to analyze first-commit discovery and monthly evolution. This produces a single markdown report summarizing AI-config creation points and governance milestones.