forensic-test-analysis
CommunityAssess test brittleness from git history.
Software Engineering#analyze#git-history#test-analysis#brittle-tests#maintenance-cost#code-forensics
AuthorAlabamaMike
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This skill helps teams identify brittle tests and maintenance burden by analyzing git history to compare test changes to production changes, enabling data-driven improvements in test health.
Core Features & Use Cases
- Brittleness measurement: compute a Test Brittleness Ratio (test_changes / production_changes) to identify unstable tests.
- Large test file detection: flag test files exceeding size thresholds to curb maintenance burden.
- Test-only commit detection: locate commits that modify only tests, signaling maintenance overhead.
- Hotspot integration readiness: correlate with hotspots and complexity trends to prioritize refactoring efforts.
- ROI guidance: estimate annual maintenance costs and potential ROI from test refactoring.
Quick Start
- Run forensic-test-analysis on your repository to extract test health metrics.
- Review the generated hotspots and maintenance recommendations, then connect with forensic-hotspot-finder for cross-analysis.
- Use forensic-refactoring-roi to estimate ROI from targeted test-suite improvements.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: forensic-test-analysis Download link: https://github.com/AlabamaMike/forensic-skills/archive/main.zip#forensic-test-analysis Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.