skills.rest
AlabamaMike
AlabamaMikeCOMMUNITY
Explore all skills by this author →
Website𝕏@alabamamikeGitHub

forensic-unplanned-work

Analyze git history to quantify unplanned work and interruption patterns.

3|2|Updated Oct 27, 2025
Search Tags:#code-quality#velocity#analyze#forensics#hotspots#git-history#unplanned-work
One-click install
npx skills add https://github.com/AlabamaMike/forensic-skills --skill forensic-unplanned-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forensic-unplanned-work
Source: https://github.com/AlabamaMike/forensic-skills/tree/main/.claude/skills/forensic-unplanned-work
Command: npx skills add https://github.com/AlabamaMike/forensic-skills --skill forensic-unplanned-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quantify unplanned work and its impact on velocity by analyzing git history to reveal interruption patterns, bug fixes, and firefighting efforts.

Core Features & Use Cases

  • Unplanned Work Ratios: compute bug/repair commits vs total commits over defined periods.
  • Interrupt Hotspots: identify files driving most unplanned work for targeted refactoring.
  • Trends & ROI-Assisted Decisions: track monthly trends and estimate velocity impact to justify quality investments.

Quick Start

Run forensic-unplanned-work on the repository to compute the last 12 months unplanned-work ratio, hotspot reports, and trend visuals.

Frequently Asked Questions about forensic-unplanned-work

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

FAQPage Schema
How do I measure unplanned work impact on velocity using git history?▼

You can quantify unplanned work impact by analyzing git history to classify commits, identify bug fixes and hotfixes, and compute the ratio of repair commits versus total commits over defined periods.

What is the best way to identify interrupt hotspots causing firefighting in a repository?▼

Interrupt hotspots are identified by analyzing git commit history to pinpoint files driving the most bug fixes and unplanned work, guiding targeted refactoring to reduce future interruptions.

Can I track monthly trends of bug fixes and unplanned work ratios across releases?▼

Yes, you can track monthly trends by calculating unplanned work ratios over defined periods, revealing interruption patterns and estimating velocity impact to support management decisions across releases.

Does forensic-unplanned-work require specific dependencies to analyze commit classification?▼

No specific dependencies are required to analyze commit classification and hotspot detection; the skill processes standardized git history metrics directly to estimate velocity impact.

How do unplanned work ratios justify code quality investments and refactoring decisions?▼

Unplanned work ratios justify code quality investments by estimating velocity impact and tracking monthly trends, providing ROI-assisted data to support management decisions for targeted refactoring.

Related Skills

Explore More Software Engineering Skills→
alangebalangeb

git-advanced

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Community
Advanced
proffesor-for-testingproffesor-for-testing
436

test-reporting-analytics

Generate and index test reporting analytics for QE metrics in CI/CD pipelines.

Community
Advanced
ailabs-393ailabs-393
438

tech-debt-analyzer

Identify and quantify technical debt across multi-language codebases.

Community
Intermediate
polsegupolsegu

retrospective

Generate sprint retrospectives by comparing plans against git commit history.

Community
Advanced