Summarizes the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing attempts, and regression history. Use when users need to: (1) Understand how a bug evolved over time, (2) Trace when and how a bug was introduced, (3) Analyze fix attempts and their effectiveness, (4) Identify regression patterns, (5) Generate bug lifecycle reports for documentation or post-mortems. Takes a repository, bug identifier, and version history as input.
91
88%
Does it follow best practices?
Impact
97%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Structured report format and key metrics
Report title format
50%
100%
Introduction section
60%
100%
Introduction When/Where/How/Context
75%
100%
Detection section
0%
100%
Detection fields
50%
100%
Fix Attempts section
100%
100%
Fix attempt details
100%
100%
Regressions section
75%
100%
Current Status section
16%
100%
Lessons Learned section
57%
100%
Time to detection metric
0%
100%
Fix attempt count metric
0%
100%
Time to resolution metric
0%
100%
Regression count metric
0%
100%
Visual timeline
100%
100%
Fix attempt patterns and introduction context analysis
Introducing commit author
100%
100%
Introducing commit date
100%
100%
Introduction change type
100%
100%
Introduction context/purpose
100%
100%
Fix attempt 1 details
100%
100%
Fix attempt 2 details
100%
100%
Fix attempt 3 details
100%
100%
Tests added documented
100%
100%
Reverted fix identified
100%
100%
Pattern: reverted = incomplete understanding
100%
100%
Pattern: multiple attempts = complexity
100%
100%
Pattern: test additions = learning
100%
100%
Lessons Learned present
100%
100%
Report follows structured format
70%
100%
Bug introduction tracing and detection documentation
Git blame referenced
100%
100%
Git bisect referenced
100%
100%
Introducing commit identified
100%
100%
Affected file and line
100%
100%
Multiple related files noted
100%
28%
Fix commit as starting point
50%
50%
Detection date
100%
100%
Detection method
100%
100%
Time to detection
100%
100%
Severity assessment
100%
100%
Introduction type of change
100%
100%
Tests at introduction time
100%
100%
Structured report format
50%
100%
Lessons Learned present
62%
100%
0f00a4f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.