git-ai-archaeology

Tracing AI configuration evolution in a Git repository involves analyzing commit history to map when AI tooling was introduced and how it matured. This skill identifies first AI-config entries, monthly commit velocity, and maturation phases, then generates a structured Markdown report for archival review.

Git archaeology for AI config maturity is the process of synthesizing repository changes into evolution phases for AI tooling. It tracks monthly commit velocity and identifies inflection points to reveal when AI configurations were introduced and how they progressed over time.

To generate a Markdown report of AI config commit velocity, invoke the skill with a path to a Git repository. It analyzes the commit history to track monthly velocity and outputs a self-contained file named {slug}-git-archaeology.md suitable for archival review.

Yes, you can identify the first commit that added AI configuration files. The skill performs first-commit tracing to pinpoint when key AI config files were introduced and by which specific commits, mapping the initial introduction of AI tooling.

No, this Git analysis tool requires no external dependencies to map AI config maturity phases. It directly analyzes the repository commit history to synthesize PRs and changes into distinct evolution phases for AI tooling.