git-metadata

Analyze Git repository history to identify churn hotspots, bus factor, bug clusters, commit velocity, and crisis patterns.

2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Integralist/agent-skills --skill git-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-metadata
Source: https://github.com/Integralist/agent-skills/tree/main/.agents/skills/git-metadata
Command: npx skills add https://github.com/Integralist/agent-skills --skill git-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive diagnostic snapshot of a Git repository, identifying churn hotspots, bus factor, bug clusters, commit velocity, and crisis patterns.

Core Features & Use Cases

  • Churn Hotspots: Identify the most-changed files in the last year.
  • Bus Factor: Analyze contributors ranked by commit count.
  • Bug Clusters: Detect files most often touched in bug-fix commits.
  • Commit Velocity: Measure commits per month.
  • Crisis Patterns: Identify reverts, hotfixes, and rollbacks.
  • Use Case: Use this Skill to quickly assess the health and stability of a codebase before a major release.

Quick Start

Analyze the Git repository and generate a report with the 'git-metadata' skill.

Frequently Asked Questions about git-metadata

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

FAQPage Schema
How do I analyze a Git repository for development health metrics?

Git repository health analysis involves extracting commit history to identify churn hotspots, bus factor, bug clusters, commit velocity, and crisis patterns. This diagnostic snapshot helps assess codebase stability and development patterns before major releases.

What is a bus factor and how is it calculated from Git history?

Bus factor is a development health metric calculated by analyzing contributors ranked by commit count within a Git repository. It identifies the minimum number of developers that need to leave a project before it stalls, indicating knowledge concentration risks.

How can I find bug clusters and churn hotspots in my codebase?

Finding bug clusters and churn hotspots requires analyzing Git commit history to detect files most frequently touched in bug-fix commits and identifying the most-changed files over the last year. This highlights unstable codebase areas requiring maintenance attention.

Do I need any specific dependencies to run Git history diagnostics?

Running Git history diagnostics requires git for repository access and analysis. No external dependencies are needed, as the Skill operates through scripts to process repository metadata and generate the development health assessment report.

Can I detect crisis patterns like reverts and hotfixes in a repository?

Detecting crisis patterns in a repository involves analyzing Git history to identify reverts, hotfixes, and rollbacks. This diagnostic capability reveals periods of instability and crisis-driven development behavior within the codebase.

What is the best way to measure commit velocity for a codebase assessment?

Measuring commit velocity for a codebase assessment is done by analyzing Git repository history to calculate commits per month. This metric evaluates development pace and consistency as part of a broader diagnostic health snapshot.