gabe-health

Analyze repository health by detecting god files, churn hotspots, coupling clusters, and bug concentration.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Brownbull/gabe-suite --skill gabe-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gabe-health
Source: https://github.com/Brownbull/gabe-suite/tree/main/skills/gabe-health
Command: npx skills add https://github.com/Brownbull/gabe-suite --skill gabe-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface structural fragility in a codebase by identifying fragile patterns such as god files, churn hotspots, coupling clusters, bug concentration, and scope creep vs plan. This helps teams anticipate risk before incidents and make informed maintenance decisions.

Core Features & Use Cases

  • God Files: Files touched in a large share of PRs/commits and likely to become bottlenecks.
  • Churn Hotspots: Most-modified files in the lookback window, highlighting unstable areas.
  • Coupling Clusters: Pairs or groups of files that frequently change together, indicating design entanglements.
  • Bug-Fix Concentration: Areas where fixes cluster, signaling fragile modules needing attention.
  • Scope Creep: Compare planned changes against actual diffs to surface unplanned work.

Quick Start

Run /gabe-health for a full baseline report.

Frequently Asked Questions about gabe-health

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

FAQPage Schema
How do I analyze codebase health to identify god files and churn hotspots?

Codebase health analysis surfaces structural fragility by identifying god files, churn hotspots, and coupling clusters. It leverages git history and plan artifacts to reveal high-risk areas, guiding maintenance and refactoring decisions before incidents occur.

What is a coupling cluster and how does it indicate design entanglement?

A coupling cluster is a group of files that frequently change together in commits, indicating design entanglements. Identifying these clusters helps reveal areas of scope creep and structural fragility requiring maintenance attention.

How do I detect scope creep by comparing planned changes against actual diffs?

Detect scope creep by comparing plan artifacts against actual git diffs to surface unplanned work. This analysis highlights deviations from the original plan, helping teams anticipate risk and manage maintenance scope effectively.

When should I run a repository fragility analysis for safer changes?

Run repository fragility analysis before epics, during retros, or after incidents to reveal high-risk areas. This timing ensures maintenance and refactoring decisions are informed by structural fragility data and bug-fix concentration patterns.

Do I need plan artifacts or .kdbp data to analyze bug-fix concentration?

No, plan artifacts and .kdbp data are optional. The analysis leverages git history to identify bug-fix concentration and structural fragility, but integrating plan artifacts provides deeper scope creep comparisons.

What is the best way to find bug-fix concentration areas in a codebase?

The best way to find bug-fix concentration areas is analyzing git commit history to surface fragile modules. Identifying where fixes cluster signals areas needing immediate maintenance and refactoring attention.