Detect Knowledge Concentration Risk

The Bus Factor Report skill helps developers and engineering managers identify "knowledge silos" within their repositories. By analyzing git history data, it pinpoints files that have only ever been touched by a single contributor and identifies authors who own a disproportionate share of the codebase.

How it works

This skill processes standard git log output to calculate ownership metrics. It scans for single-owner files (BFR001) and flags high-risk components—those frequently changed but only understood by one person (BFR002). It provides a high-level summary including an estimated truck factor and per-author ownership percentages.

Why use this skill?

Risk Mitigation: Proactively identify critical systems that would be unsupported if a key developer left the project.
Onboarding Strategy: Determine exactly which files require pair programming or documentation to spread knowledge.
Data-Driven Insights: Move beyond "gut feelings" about code ownership with concrete authorship stats.
Non-Intrusive: It parses text logs rather than requiring direct shell access, making it safe for use in restricted environments.

Output format

The skill generates a structured report identifying specific high-risk files, author concentration percentages, and an overall Bus Factor score, accompanied by remediation suggestions.