What is an 'interrupt hotspot' in this context?

An interrupt hotspot is a specific file that has a high volume of bug fixes (typically >10 per year) and where more than 50% of the changes are fixes rather than new features.

Why does the skill reference Google SRE and DevOps research?

It uses these industry benchmarks to provide context for your data, such as the fact that unplanned work exceeding 40% is a primary driver of low team morale and burnout.

How does the skill differentiate between planned and unplanned work?

It analyzes git commit messages using a classification pattern that looks for keywords such as 'fix', 'bug', and 'hotfix' for unplanned work, versus 'feat' or 'add' for planned work.

Can this skill help calculate the ROI of refactoring?

Yes. By identifying files that cause the most unplanned work, it can estimate how much developer capacity (FTE) would be regained by reducing the bug ratio in those specific areas.

Forensic Unplanned Work Analysis

Name: Forensic Unplanned Work Analysis
Author: AlabamaMike

byAlabamaMike

분석 및 모니터링

Analyzes git history to quantify unplanned work, identify interrupt hotspots, and measure the impact of technical debt on team velocity.

소개

This skill empowers Claude to perform forensic analysis on codebases by classifying git commits into unplanned work (bugs/hotfixes) and planned features. It calculates the unplanned work ratio, identifies high-maintenance 'interrupt hotspots,' and tracks quality trends over time. By referencing industry research from Google SRE and DevOps studies, it helps teams visualize the productivity cost of technical debt and justifies quality investments through data-driven ROI calculations.

주요 기능

Identifies interrupt hotspots with high bug-to-feature ratios
Provides research-backed benchmarks for team morale and productivity
Classifies commits into unplanned, planned, and refactoring categories
Generates monthly trend reports to visualize quality degradation
0 GitHub stars
Calculates Velocity Impact in terms of Full-Time Equivalent (FTE) loss

사용 사례

Diagnosing why team velocity is declining over several sprints
Justifying refactoring budgets to stakeholders using concrete ROI data
Conducting quarterly codebase health checks to monitor technical debt

소개

주요 기능

Identifies interrupt hotspots with high bug-to-feature ratios
Provides research-backed benchmarks for team morale and productivity
Classifies commits into unplanned, planned, and refactoring categories
Generates monthly trend reports to visualize quality degradation
0 GitHub stars
Calculates Velocity Impact in terms of Full-Time Equivalent (FTE) loss

사용 사례

Diagnosing why team velocity is declining over several sprints
Justifying refactoring budgets to stakeholders using concrete ROI data
Conducting quarterly codebase health checks to monitor technical debt