How does the skill help identify the 'bus factor'?

It analyzes the distribution of commits across different contributors for specific files and directories, highlighting areas where only one person has significant knowledge.

Can I limit the analysis to a specific timeframe?

Yes, you can specify a time range in months to focus on recent development patterns and current team knowledge rather than the entire project history.

What is temporal coupling in this context?

Temporal coupling refers to files that are frequently changed together in the same commits. This helps identify hidden dependencies that might not be obvious through static code analysis.

What counts as a 'hotspot'?

Hotspots are files with high change frequency (churn). These are often areas of high complexity or technical debt that represent the best candidates for refactoring.

Does this work on specific subdirectories?

Absolutely. You can run the analysis on the entire repository or target a specific folder to get more granular insights into a particular module.

Git History & Knowledge Analyzer

Name: Git History & Knowledge Analyzer
Author: lis186

bylis186

•

Analytics & Monitoring

Analyzes Git commit history to identify codebase hotspots, hidden file dependencies, and knowledge distribution risks.

The History Analyzer skill provides deep visibility into your repository's evolution by parsing git history to find frequently changed files and temporal coupling where files consistently change together. It helps teams identify 'bus factor' risks by mapping contributor expertise and knowledge silos, making it an essential tool for onboarding, planning refactoring efforts, and improving team collaboration through data-driven insights.

Key Features

01Generate prioritized lists of files requiring refactoring or documentation

0221 GitHub stars

03Identify codebase hotspots and high-churn files indicating technical debt

04Detect temporal coupling and hidden architectural dependencies between files

05Map contributor distribution and subject matter expertise across directories

06Calculate bus factor risks for critical modules and single-contributor areas

Use Cases

01Onboarding new developers by identifying the primary experts for specific modules

02Auditing repository health to mitigate knowledge silos and single-point-of-failure risks

03Targeting refactoring efforts toward high-complexity files with the most frequent changes

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lis186/sourceatlas history-analyzer

For use in Claude.ai and ChatGPT

Download Skill