git-ai-archaeology

Analyze git history to reveal first commits, monthly velocity, and major PRs for AI config paths.

37|4|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/FlorianBruniaux/claude-code-plugins --skill git-ai-archaeology-florianbruniaux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-ai-archaeology
Source: https://github.com/FlorianBruniaux/claude-code-plugins/tree/main/plugins/ai-methodology/skills/git-ai-archaeology
Command: npx skills add https://github.com/FlorianBruniaux/claude-code-plugins --skill git-ai-archaeology-florianbruniaux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes git history to reveal how AI configuration files evolve over time, providing visibility into creation, velocity, and major changes across the repository.

Core Features & Use Cases

  • First-commit discovery for key AI-config paths and the evolution timeline.
  • Monthly distribution of AI-config commits with high-level trends and maturity insights.
  • Identification of major PRs and cross-path changes that shaped the AI config stack.

Quick Start

Run the analysis against a local Git repository to generate a markdown report named git-ai-archaeology-git-archaeology.md.

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 in a git repository?

Analyze git history to reveal AI config evolution by tracking first commits per AI-config path, monthly commit velocity, and major PRs. The tool outputs a structured markdown file detailing how configurations matured over time.

How does git history analysis reveal AI configuration maturity?

Git history analysis reveals AI configuration maturity by calculating first commits per config path, monthly commit velocity, and mapping major PRs. This tracks how AI configurations have matured across paths and releases.

Can I analyze any local git repository for AI tooling changes?

Yes, you can analyze any local git repository containing AI-related configuration, policies, or tooling. You must provide a local repo_path to execute git commands and generate the markdown configuration maturity report.

What is the best way to find the first commit for AI config paths?

The best way to find first commits for AI config paths is using git history analysis. It identifies initial commits for key AI-config paths, tracks monthly commit distribution, and outputs a structured markdown timeline report.

Do I need a CHANGELOG file to analyze AI config commit velocity?

No, a CHANGELOG file is not required to analyze AI config commit velocity. The tool uses git commands to calculate monthly distributions and optionally consults a CHANGELOG when available for major PR context.

What format does the git AI archaeology report output?

The git AI archaeology report outputs a structured markdown file named git-ai-archaeology-git-archaeology.md. This file contains global metrics, first-commit data, monthly distributions, and major PR insights.