history-analyzer_skill

Overview

This skill analyzes a repository's git history to surface hotspots, coupling, and knowledge distribution. It helps teams quickly see which files change most, which files tend to change together, and who knows which parts of the code. Use it to assess risk, prioritize refactoring, and plan knowledge transfers.

How this skill works

The analyzer inspects commit metadata across the repo or a specified path and time range. It computes metrics such as change frequency, temporal coupling (files changed together), and contributor footprints to estimate bus factor and knowledge silos. Results are returned as ranked hotspots, coupling groups, recent contributors per area, and suggested actions.

When to use it

• You want to find files that change most often or are most volatile
• You need to know who to ask about a particular module or file
• You suspect hidden dependencies because files often change together
• You want to measure bus factor and identify single-contributor risks
• Preparing a refactor or onboarding plan and need priority targets

Best practices

• Run the analysis for the whole repo and for focused directories to compare views
• Specify a time window (e.g., last 6 months) to focus on recent activity
• Combine hotspot data with code complexity metrics for better prioritization
• Use contributor lists to plan pairings or documentation for high-risk areas
• Re-run after major releases to track how hotspots and coupling evolve

Example use cases

• Ask "What are the hotspots in this codebase?" to get a ranked list of volatile files
• Query "Who knows the payment module best?" to produce recent contributor scores for that directory
• Investigate "What files always change together?" to uncover hidden coupling before refactoring
• Check "Is there any bus factor risk?" to find files owned by a single person
• Generate priority actions: files to refactor, tests to add, or developers to involve