skills.rest
lis186
lis186COMMUNITY
Explore all skills by this author →
GitHub

history-analyzer

Analyze git history to identify hotspots, coupling, and knowledge distribution.

46|4|Updated Nov 19, 2025
Search Tags:#coupling#analyze#hotspots#git-history#bus-factor#code-evolution#contributor-distribution
One-click install
npx skills add https://github.com/lis186/SourceAtlas --skill history-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: history-analyzer
Source: https://github.com/lis186/SourceAtlas/tree/main/plugin/skills/history-analyzer
Command: npx skills add https://github.com/lis186/SourceAtlas --skill history-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams understand code evolution by identifying hotspots, hidden couplings, and knowledge distribution across a codebase.

Core Features & Use Cases

  • Identify hotspots: files with frequent changes.
  • Detect coupling between files that change together.
  • Assess knowledge distribution and bus factor.
  • Use Case: Onboarding new engineers or planning refactors.

Quick Start

Run /sourceatlas:history for the entire repository, or /sourceatlas:history <path> for a specific directory.

Frequently Asked Questions about history-analyzer

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

FAQPage Schema
How do I identify code hotspots and frequently changed files in a git repository?▼

Detect temporal coupling in your codebase by analyzing git history to find files that frequently change together. This Skill surfaces hidden dependencies between modules, enabling teams to assess structural risks and plan decoupling refactors.

How do I assess bus factor and contributor distribution for a specific directory?▼

Assess bus factor and contributor distribution by analyzing git history for specific directories. This Skill evaluates ownership and change patterns over time, revealing knowledge silos and onboarding risks for engineering teams.

What is temporal coupling and how does analyzing git history reveal hidden dependencies?▼

Temporal coupling occurs when files change together frequently in git history. This Skill analyzes commit data to detect these hidden dependencies, helping teams understand structural relationships and evaluate code evolution risks.

Can I analyze code evolution for a specific directory instead of the entire repository?▼

Yes, you can analyze code evolution for a specific directory instead of the entire repository. This Skill accepts a path parameter to scope hotspot detection, coupling metrics, and contributor distribution to targeted codebase areas.

Does analyzing git history for knowledge distribution require any external dependencies?▼

Analyzing git history for knowledge distribution requires no external dependencies. This Skill operates directly on repository commit data to evaluate ownership, contributor distribution, and change patterns without needing additional tools.

Related Skills

Explore More Software Engineering Skills→
GabeujinGabeujin

repo-story-time

Analyze repository structure and commit history to generate summary and narrative documents.

Community
Advanced
j4hr3nj4hr3n

recon

Analyze git history and project metrics to generate a codebase health report.

Community
Advanced
dinoudondinoudon

code-quality-metrics

Assess code quality using cyclomatic complexity, test coverage, and maintainability metrics.

Community
Advanced
ByronWilliamsCPAByronWilliamsCPA

retro

Computes git commit analytics for development retrospective reports.

Official
Intermediate