Claude Skill

git-ai-archaeology

Analyze AI config evolution in a git repo — first commits per path, monthly distribution, major PRs, maturity phases

Reviewed community sourceInstallable6 sections3 related pages

Editor's Note

Analyze AI config evolution in a git repo — first commits per path, monthly distribution, major PRs, maturity phases Covers expected input, workflow, step 1: verification and global metrics.

Editorial Guide

What to do with this skill

Start with the workflow below, then drop into the upstream source only after the page has narrowed the job for you.

What this skill does

Analyze AI config evolution in a git repo — first commits per path, monthly distribution, major PRs, maturity phases

When to use it

Use it when you need Claude Code to follow the workflow defined in the upstream source instead of improvising from generic examples.

Install and setup notes

  • Open the upstream source before treating this page as install-ready, because not every official record is meant to be dropped into a workflow unchanged.
  • Keep the context narrow. These skills are usually strongest when you load only the branch, reference set, or workflow step that matches the current task.
  • If you plan to standardize on this skill for team use, pin the upstream repo and check for updates periodically instead of assuming the official defaults are static.

Example workflow

  1. Start with one narrow task that obviously fits the scope of this Claude Code skill instead of pulling it into every job by default.
  2. Read the overview and first source section, then choose the smallest branch of guidance or references that solves the task in front of you.
  3. Run the change on a real file, command, or workflow, verify the result, and only then widen the skill into a repeatable team pattern.

Compatible agents

This skill is explicitly marked for Claude Code.

Claude Code

Install source

This page does not expose a single copy-paste install command in the normalized record. Use the upstream install source below to confirm the exact steps, file paths, and current setup expectations before you add it to your stack.

Page Outline

Expected InputWorkflowStep 1: Verification and Global MetricsStep 2: Section 1 — First Commits per AI-Config PathStep 3: Section 2 — Monthly Distribution of AI-Config CommitsStep 4: Section

Source Content

Normalized top-level metadata comes from the directory layer. The body below is the upstream source content for this item.

git-ai-archaeology

Produces a complete analysis of AI config evolution in a git repository. Finds when each AI configuration file was created, how AI-config commit velocity evolved month by month, which PRs structured the evolution, and identifies maturity phases.

**Output**: a single file `{output_dir}/{slug}-git-archaeology.md`

Expected Input

/git-ai-archaeology repo_path=/path/to/repo [output=./talks/slug] [slug=talk-name] [since=2025-01-01]
  • `repo_path`: absolute path to the target git repo (required)
  • `output`: output directory (default: `./talks`)
  • `slug`: output filename (default: repo folder name)
  • `since`: analysis start date (default: first repo commit)

Workflow

  • **Verify the repo**: ensure the path exists and is a git repo
  • **Global metrics**: total commits, releases, contributors, time period
  • **Section 1 — First commits**: find creation date for key AI-config paths
  • **Section 2 — Monthly distribution**: commits filtered by AI-config keywords
  • **Section 3 — Major PRs**: extract and categorize significant AI-config commits
  • **Section 4 — CHANGELOG**: if CHANGELOG.md exists, extract releases with AI mentions
  • **Section 5 — Phases**: synthesize evolution phases
  • **Save** the output file

---

Step 1: Verification and Global Metrics

# Verify it's a git repo
git -C {repo_path} rev-parse --git-dir

# Global metrics
git -C {repo_path} log --oneline | wc -l                                    # total commits
git -C {repo_path} tag --sort=version:refname | wc -l                       # total releases
git -C {repo_path} shortlog -sn --no-merges | wc -l                         # contributors
git -C {repo_path} log --pretty=format:"%ad" --date=short | tail -1         # first commit
git -C {repo_path} log --pretty=format:"%ad" --date=short | head -1         # last commit
git -C {repo_path} log --merges --oneline | wc -l                           # merged PRs

---

Step 2: Section 1 — First Commits per AI-Config Path

For each path, find the origin commit with `--diff-filter=A`:

# Paths to analyze — adapt based on what exists in the repo
PATHS=(
  "CLAUDE.md"
  ".claude"
  ".claude/commands"
  ".claude/agents"
  ".claude/hooks"
  ".claude/skills"
  ".claude/rules"
  ".agents"
  ".cursor"
  "doc/knowledge-base.md"
  "doc/guides/ai-instructions"
  "doc/guides/ai-review"
)

for path in "${PATHS[@]}"; do
  git -C {repo_path} log --diff-filter=A --follow \
    --format="%ad | %H | %s" --date=short \
    -- "$path" | tail -1
done

Build the Section 1 table from results. Skip paths with no output (don't exist in this repo).

Also build the ASCII timeline:

{date} ─── {path} ─── {message}

Sorted chronologically.

---

Step 3: Section 2 — Monthly Distribution of AI-Config Commits

Filter commits by AI-config-related keywords:

# All commits with AI-config keywords
git -C {repo_path} log --format="%H %s" | \
  grep -iE "(claude|feat.ai|docs.ai|tech.ai|mcp|skill|hook|agent|llm|prompt)" \
  > /tmp/ai_commits_filtered.txt

# Count AI-config commits per month
git -C {repo_path} log --format="%ad %H" --date=format:"%Y-%m" | \
  while read month hash; do
    if grep -q "$hash" /tmp/ai_commits_filtered.txt; then
      echo "$month"
    fi
  done | sort | uniq -c

More direct alternative:

git -C {repo_path} log --format="%ad %s" --date=format:"%Y-%m" | \
  grep -iE " (feat|fix|docs|tech|chore|refactor)\(ai\)|claude|mcp.*server|\.claude/|skill|hook.*security|guardrail" | \
  awk '{print $1}' | sort | uniq -c

Compute per month:

  • AI-config commit count
  • % of monthly total (cross-reference with all-category monthly total)
  • Context (if notable period)

Build ASCII distribution chart (horizontal or vertical bars).

---

Step 4: Section

<!-- truncated -->

Recommended skills

Next places to browse

Sponsored
MoltAwards: Turn AI agents loose on government contracts & jobs! logo

Turn AI agents loose on government contracts

Learn more