git-xray

Run five diagnostic git commands and generate a repository health report.

2|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/nibzard/skills --skill git-xray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-xray
Source: https://github.com/nibzard/skills/tree/main/skills/git-xray
Command: npx skills add https://github.com/nibzard/skills --skill git-xray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before reading code, this skill builds a strategic picture of a repository by running five diagnostic git commands to reveal hotspots, who touched what, where bugs cluster, momentum, and firefighting signals.

Core Features & Use Cases

  • Five diagnostic Git commands run in order to surface hotspots, contributions, defects, momentum, and firefighting signals.
  • Structured health report highlighting churn hotspots, bug clusters, bus-factor risk, momentum trends, and a recommended reading order.
  • Use case: When asked to understand a new repo, generate a concise health snapshot before diving into code.

Quick Start

Ask me to generate a Git X-Ray health report for a specific repository.

Frequently Asked Questions about git-xray

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

FAQPage Schema
How do I check repository health before reading a new codebase?

A git health check identifies and quantifies repository hotspots before you read the code. It runs diagnostic git commands to reveal churn, bug clusters, momentum, and firefighting signals, producing an actionable report with a recommended reading order.

What is codebase churn analysis and when do I need it?

Codebase churn analysis identifies files with high modification rates to signal instability. You need it for strategic reads, due diligence, and risk assessment across repositories of any size to pinpoint exactly where defects cluster and momentum shifts.

Can I assess bus-factor risk and bug clusters in repositories of any size?

Yes, you can assess bus-factor risk and bug clusters in repositories of any size. The diagnostic process executes five git commands to cross-reference contribution data and defect history, returning a structured health report highlighting these specific firefighting signals.

How do I generate a code review report that recommends a reading order?

Generate a code review report by running five diagnostic git commands in sequence to surface contributions, defects, and momentum. The cross-referenced output produces a structured health report that includes a recommended reading order for the codebase.

Does this repository risk assessment require any external dependencies?

No, this repository risk assessment requires no external dependencies. It executes five diagnostic git commands directly against the codebase to cross-reference outputs and produce the health report without needing additional components.