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.
npx skills add majiayu000/claude-skill-registry --skill bug-history-summarizer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 - **Version range**: Specific versions/commits to analyze (or entire history) - **Related artifacts**: Issue reports, pull requests, commit messages, test results ### 2. Trace Bug Introduction Identify when and how the bug was introduced: **Using git blame and bisect:** - Run `git blame` on affected files to find when problematic lines were added - Use `git bisect` to pinpoint the exact commit that introduced the bug - Analyze the introducing commit: author, date, purpose, related changes **Analyze introduction context:** - What was the original intent of the change? - Was it a new feature, refactoring, or bug fix? - Were there code review comments or warnings? - What tests existed at the time? ### 3. Track Detection History Document when and how the bug was discovered: - **Initial detection**: When was the bug f
- Workflow
- 1. Identify the Bug and Gather Context
- 2. Trace Bug Introduction
- 3. Track Detection History
- 4. Analyze Fix Attempts
- 5. Check for Regressions
- 6. Generate Summary Report
- Example
- Output Format
- Git Commands Reference
- Tips for Effective Bug History Analysis
Find when a line was introduced git blame <file> Find the commit that introduced a bug git bisect start git bisect bad <bad-commit> git bisect good <good-commit> Search commit messages for bug references git log --grep="<bug-id>" --oneline Show commits that modified a specific file git log --follow -- <file>
What does the bug-history-summarizer skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill bug-history-summarizer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.