git-ai-archaeology

Analyze AI configuration evolution in a git repository and output a markdown report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reproducible way to uncover the historical evolution of AI-related configuration and tooling inside a git repository, answering when specific AI config files appeared, how commit activity changed over time, which pull requests drove changes, and what maturity phases the project went through.

Core Features & Use Cases

  • First-commit discovery: locate the origin commit for common AI-config paths (.claude, .agents, CLI files, docs) and produce a chronological creation timeline.
  • Monthly distribution & trends: compute AI-config commit velocity per month, percentage of repo activity, and ASCII visualizations to highlight inflection points.
  • Major PRs and phase synthesis: extract PR/merge commit candidates related to AI tooling, analyze CHANGELOG mentions if present, and synthesize evidence-based maturity phases into a single markdown report.
  • Use Case: security reviewers, engineering managers, and maintainers can audit AI configuration adoption and identify when infrastructure or guardrails were introduced.

Quick Start

Run the skill against a local git repository path to generate a single markdown report summarizing AI-config first commits, monthly trends, major PRs, changelog findings, and evolution phases.

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 the history of AI configuration files in a git repository?

Tracking AI configuration history in a git repository involves analyzing commit logs to locate first commits for paths like .claude or .agents, aggregating monthly commit distributions, and extracting PR candidates to generate a chronological markdown report.

What is git archaeology for AI tooling adoption?

Git archaeology for AI tooling adoption is the process of uncovering the historical evolution of AI configs inside a repository to answer when specific files appeared, how commit activity changed, and what maturity phases the project went through.

Can I find when a specific AI config file was first added to my repo?

Yes, finding when a specific AI config file was first added involves locating the origin commit for common AI-config paths and producing a chronological creation timeline as part of a markdown report.

Does analyzing git timelines for AI configs require special access?

Analyzing git timelines for AI configs requires git CLI access and a readable local repository path to compute commit velocity and identify major PRs without needing external dependencies.

How do I identify which pull requests drove changes to AI tooling?

Identifying which pull requests drove changes to AI tooling involves extracting PR and merge commit candidates related to AI configs, analyzing CHANGELOG mentions if present, and synthesizing evidence-based maturity phases into a report.

What is the best way to visualize AI commit velocity over time?

Visualizing AI commit velocity over time is best achieved by computing monthly AI-config commit distributions, calculating the percentage of repo activity, and generating ASCII visualizations to highlight inflection points.