Individual skill
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.
skills/bug-history-summarizer/SKILL.md
Source commit 4f38503747e0617504bce5329283ef837d375c09
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 260
- Repository last updated
- Aug 21, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-skills Repository topic
- metaprogramming Repository topic
- software-development Repository topic
- software-engineering Repository topic
- claude Repository topic
- claude-code Repository topic
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Bug History Summarizer
Trace and summarize the complete lifecycle of a bug across code versions.
## Workflow
Follow these steps to generate a comprehensive bug history summary:
### 1. Identify the Bug and Gather Context
Collect essential information:
- **Bug identifier**: Issue number, commit hash, or bug description
- **Repository**: Target codebase with version history