bug-history-summarizer

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.

Install with Tessl CLI

npx tessl i github:ArabelaTso/Skills-4-SE --skill bug-history-summarizer

What are skills?

Review — 88%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

54%

Bug History Report: Session Expiry Race Condition

Structured report format and key metrics

Criteria

Without context

With context

Report title format

50%

100%

Introduction section

60%

100%

Introduction When/Where/How/Context

75%

100%

Detection section

100%

Detection fields

50%

100%

Fix Attempts section

100%

Fix attempt details

100%

Regressions section

75%

100%

Current Status section

16%

100%

Lessons Learned section

57%

100%

Time to detection metric

100%

Fix attempt count metric

100%

Time to resolution metric

100%

Regression count metric

100%

Visual timeline

100%

Without context: $0.2078 · 3m 11s · 10 turns · 15 in / 3,895 out tokens

With context: $0.3558 · 3m 17s · 12 turns · 92 in / 5,933 out tokens

100%

Bug Lifecycle Analysis: Order Total Calculation Error

Fix attempt patterns and introduction context analysis

Criteria

Without context

With context

Introducing commit author

100%

Introducing commit date

100%

Introduction change type

100%

Introduction context/purpose

100%

Fix attempt 1 details

100%

Fix attempt 2 details

100%

Fix attempt 3 details

100%

Tests added documented

100%

Reverted fix identified

100%

Pattern: reverted = incomplete understanding

100%

Pattern: multiple attempts = complexity

100%

Pattern: test additions = learning

100%

Lessons Learned present

100%

Report follows structured format

70%

100%

Without context: $0.2233 · 2m 39s · 8 turns · 13 in / 3,561 out tokens

With context: $0.5449 · 5m 43s · 21 turns · 27 in / 7,612 out tokens

91%

Trace a Data Export Bug for Post-Mortem Documentation

Bug introduction tracing and detection documentation

Criteria

Without context

With context

Git blame referenced

100%

Git bisect referenced

100%

Introducing commit identified

100%

Affected file and line

100%

Multiple related files noted

100%

28%

Fix commit as starting point

50%

Detection date

100%

Detection method

100%

Time to detection

100%

Severity assessment

100%

Introduction type of change

100%

Tests at introduction time

100%

Structured report format

50%

100%

Lessons Learned present

62%

100%

Without context: $0.2018 · 1m 58s · 8 turns · 11 in / 3,128 out tokens

With context: $0.4128 · 3m 47s · 18 turns · 23 in / 5,244 out tokens

Evaluated: about 11 hours ago
Agent: Claude Code

Table of Contents

Bug History Report: Session Expiry Race Condition Bug Lifecycle Analysis: Order Total Calculation Error Trace a Data Export Bug for Post-Mortem Documentation

Is this your skill?

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.