hotspot-detective

Identify high-churn files in Git repositories using churn and complexity signals.

1|Updated Feb 17, 2026

Search Tags:#git #complexity #refactor #code-quality #hotspots #churn #temporal-coupling

Ready to run

npx skills add https://github.com/snqb/my-skills --skill hotspot-detective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hotspot-detective
Source: https://github.com/snqb/my-skills/tree/main/hotspot-detective
Command: npx skills add https://github.com/snqb/my-skills --skill hotspot-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify high-churn files in a codebase to surface hotspots.

Core Features & Use Cases

Surface top churn hotspots via Git history.
Analyze temporal coupling and related complexity signals.
Prioritize candidate files for refactoring or deeper investigation.

Quick Start

Run the hotspot detector to identify files with the highest churn in your codebase.

Frequently Asked Questions about hotspot-detective

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

FAQPage Schema

How do I identify high-churn files in a Git repository to find refactoring targets?▼

Git forensics identifies code hotspots by analyzing recent repository history to surface files with high churn, temporal coupling, and complexity, helping prioritize candidates for refactoring or deeper investigation.

What are code hotspots and how does temporal coupling indicate refactoring needs?▼

Code hotspots are files with high churn and complexity. Temporal coupling identifies files frequently changed together in Git commits, revealing hidden dependencies and prioritizing refactoring targets to improve code quality.

Can I analyze code complexity and churn in any standard project layout using Git tooling?▼

Yes, hotspot detection requires Git tooling and assumes a standard project layout. It analyzes repositories across recent history to surface files with high churn, complexity, and refactoring needs.

What's the best way to surface top churn hotspots via Git history?▼

The best way to surface top churn hotspots is running a detector that analyzes Git history to evaluate churn rates, temporal coupling, and complexity signals, generating a prioritized list of volatile files for refactoring.

Does this code quality analysis work with repositories that have limited commit history?▼

This analysis applies to Git repositories across recent history. Repositories with limited commit history may lack sufficient churn and temporal coupling signals to effectively surface complexity hotspots or prioritize refactoring needs.