git-archaeology

Analyze git repository history to generate a structured health diagnostic report.

Updated May 11, 2025
One-click install
npx skills add https://github.com/rogsme/dotfiles --skill git-archaeology-rogsme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-archaeology
Source: https://github.com/rogsme/dotfiles/tree/main/.claude/skills/git-archaeology
Command: npx skills add https://github.com/rogsme/dotfiles --skill git-archaeology-rogsme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive analysis of a git repository's history, health, and risk areas, allowing users to understand the codebase's evolution and potential issues before diving into the source code.

Core Features & Use Cases

  • Repository Analysis: Analyze the entire history or a specific part of a git repository.
  • Health Diagnostic: Identify churn hotspots, bus factor, bug clusters, and other health indicators.
  • Report Generation: Generate a structured GIT-ARCHAEOLOGY.md report with findings, analysis, and recommendations.
  • Use Case: Before reading source code, use this Skill to get a quick overview of the repository's health and potential areas of concern.

Quick Start

Analyze the history of the 'src/api' directory in the current repository for the last 6 months.

Frequently Asked Questions about git-archaeology

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

FAQPage Schema
How do I analyze git repository history to identify churn hotspots and bus factor?

To analyze git repository history, this Skill examines the commit log to produce a structured diagnostic report identifying churn hotspots, bus factor, and bug clusters. It generates a GIT-ARCHAEOLOGY.md file containing findings, analysis, and actionable recommendations.

What is the best way to check codebase health before reading the source code?

Checking codebase health before reading source code is best done by analyzing git history for risk areas. This Skill evaluates repository evolution to output a structured report with health indicators, allowing you to understand potential issues and codebase health before diving in.

Can I analyze a specific directory of a git repository instead of the entire codebase?

Yes, you can analyze a specific directory of a git repository instead of the entire codebase. The repository analysis can target the entire history or a specific part of the git repository, allowing you to focus the diagnostic report on particular subdirectories or modules.

Do I need to install any dependencies to generate a git repository diagnostic report?

You do not need to install external dependencies to generate a git repository diagnostic report, but the Skill requires git and its internal scripts to perform the analysis. These scripts execute the repository history queries and generate the final structured report output.

What specific health indicators are included in a git archaeology analysis report?

A git archaeology analysis report includes specific health indicators such as churn hotspots, bus factor, and bug clusters. These health indicators are compiled into a structured GIT-ARCHAEOLOGY.md document that provides findings, analysis, and recommendations for the repository.