New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bug History Summarizer

by ArabelaTso in ArabelaTso/Skills-4-SE

Summarizes the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing attempts, and regression history.

Apache-2.0Auto-check passedDevelopment

Install Bug History Summarizer

skills CLI
$ npx skills add ArabelaTso/Skills-4-SE --skill bug-history-summarizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ArabelaTso/Skills-4-SE bug-history-summarizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bug-history-summarizer .claude/skills/bug-history-summarizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bug-history-summarizer
GitHub stars
253
Token cost
~1.8k tokens
SKILL.md length
522 words
Files
1
Skills in repo
170
Repo updated
First seen
Licence
Apache-2.0

At a glance

Summarizes the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing attempts, and regression history.

  • Works in 6 steps: Identify the Bug and Gather Context → Trace Bug Introduction → Track Detection History → …
  • Understand how a bug evolved over time
  • SKILL.md covers Workflow, Example, Output Format and Git Commands Reference, plus 1 more section
  • Calls git

What it does

Bug History Summarizer is an agent skill from ArabelaTso/Skills-4-SE. 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.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Runbooks and postmortems. It works with Git. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.

When your agent uses it

  • Understand how a bug evolved over time
  • Trace when and how a bug was introduced
  • Analyze fix attempts and their effectiveness
  • Identify regression patterns

Example prompts

  • “Use the bug-history-summarizer skill to summariz the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing…”
  • “/bug-history-summarizer”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 4f38503. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bug History Summarizer loads about 1.8k tokens when it runs. Until then it costs about 125 tokens; SKILL.md has 522 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~125
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 522 words, ~1,772 tokens.

Download SKILL.mdSave it as .claude/skills/bug-history-summarizer/SKILL.md (or your agent's skills folder).
name
bug-history-summarizer
description
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.

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 first reported or noticed?
  • Detection method: User report, automated test, code review, production incident?
  • Time to detection: How long between introduction and discovery?
  • Severity assessment: How was the bug initially classified?
4. Analyze Fix Attempts

Chronicle all attempts to fix the bug:

For each fix attempt:

  • Commit hash and date
  • Author and reviewer
  • Fix approach and code changes
  • Test coverage added
  • Whether the fix was successful or reverted

Identify patterns:

  • Multiple fix attempts indicate complexity
  • Reverted fixes suggest incomplete understanding
  • Test additions show learning from the bug
5. Check for Regressions

Identify if the bug reappeared after being fixed:

  • Search for related bug reports after the fix
  • Check if the fix was reverted or modified
  • Look for similar bugs in related code
  • Analyze if the bug reoccurred in different contexts
6. Generate Summary Report

Create a structured timeline and analysis:

Timeline format:

markdown
## Bug History: [Bug Title/ID]

### Introduction
- **When**: [Date/Commit]
- **Where**: [File:Line]
- **How**: [Description of introducing change]
- **Context**: [Why the change was made]

### Detection
- **Discovered**: [Date]
- **Method**: [How it was found]
- **Time to Detection**: [Duration]
- **Initial Impact**: [Severity/Scope]

### Fix Attempts
1. **Attempt 1** ([Date/Commit])
   - Approach: [Description]
   - Outcome: [Success/Failure/Partial]
   - Tests Added: [Yes/No]

2. **Attempt 2** ([Date/Commit])
   - ...

### Regressions
- **Regression 1** ([Date])
  - Cause: [Why it reappeared]
  - Fix: [How it was resolved]

### Current Status
- [Fixed/Open/Recurring]
- Last modified: [Date]

### Lessons Learned
- [Key insights from the bug's history]
Show full SKILL.md (234 more words)Show less

Example

Input:

  • Repository: myapp
  • Bug: "Null pointer exception in user login"
  • Issue: #456

Analysis Process:

  1. Git blame shows the problematic code was added in commit abc123 on 2024-01-15
  2. Commit analysis reveals it was part of a refactoring to improve performance
  3. Issue tracker shows bug reported on 2024-02-20 (36 days after introduction)
  4. Fix attempts:
    • First fix (commit def456, 2024-02-21): Added null check, but incomplete
    • Second fix (commit ghi789, 2024-02-25): Comprehensive fix with tests
  5. Regression check: No regressions found

Generated Summary:

markdown
## Bug History: Null Pointer Exception in User Login (#456)

### Introduction
- **When**: 2024-01-15 (commit abc123)
- **Where**: src/auth/LoginHandler.java:45
- **How**: Refactoring removed null check during performance optimization
- **Context**: Part of PR #234 to reduce login latency

### Detection
- **Discovered**: 2024-02-20
- **Method**: Production incident report
- **Time to Detection**: 36 days
- **Initial Impact**: High severity - blocking user logins

### Fix Attempts
1. **Attempt 1** (2024-02-21, commit def456)
   - Approach: Added null check for user object
   - Outcome: Partial - fixed main case but missed edge case
   - Tests Added: Yes (1 unit test)

2. **Attempt 2** (2024-02-25, commit ghi789)
   - Approach: Comprehensive null handling with validation
   - Outcome: Success
   - Tests Added: Yes (3 unit tests + 1 integration test)

### Regressions
- None detected

### Current Status
- Fixed (as of 2024-02-25)
- Last modified: commit ghi789

### Lessons Learned
- Performance optimizations should maintain defensive checks
- Initial fix was too narrow - comprehensive testing revealed edge cases
- Added regression tests to prevent reintroduction

Output Format

Provide:

  1. Structured timeline in Markdown format
  2. Key metrics:
    • Time to detection
    • Number of fix attempts
    • Time to resolution
    • Regression count
  3. Visual timeline (optional, using ASCII or Mermaid):
    2024-01-15: Bug introduced (commit abc123)
     |
     | (36 days)
     |
2024-02-20: Bug detected (issue #456)
     |
     | (1 day)
     |
2024-02-21: Fix attempt 1 (partial)
     |
     | (4 days)
     |
2024-02-25: Fix attempt 2 (success)
  4. Lessons learned and recommendations

Git Commands Reference

Useful commands for bug history analysis:

bash
# 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>

# Show commits in a date range
git log --since="2024-01-01" --until="2024-12-31"

# Find commits by author
git log --author="<name>"

# Show detailed commit information
git show <commit-hash>

Tips for Effective Bug History Analysis

  1. Start with the fix - Work backwards from the fix commit to understand the bug
  2. Check related files - Bugs often span multiple files
  3. Read commit messages - They provide context about intent
  4. Review pull requests - Comments reveal decision-making
  5. Check test history - Tests added after bugs show learning
  6. Look for patterns - Similar bugs may have related causes
  7. Consider context - Deadlines, team changes, and technical debt affect bug introduction

© ArabelaTso, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/bug-history-summarizer of ArabelaTso/Skills-4-SE.

Open the folder on GitHubat commit 4f38503

Compare with similar skills

Bug History Summarizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bug History Summarizer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug History Summarizer this skillArabelaTso/Skills-4-SE253—~1.8kAutomated safety check: PassApache-2.0
Change Documentation Writerjsmastery-pro/skills1.5k—~2.4kAutomated safety check: NotesMIT
GreptimeDB Release RunbookGreptimeTeam/greptimedb6.7k—~1.4kAutomated safety check: PassApache-2.0
Post Mortemhanamizuki/solopreneur152—~1.7kAutomated safety check: PassMIT
AI Project Memorytudoumashu/ai-memory-skillpack456—~1.1kAutomated safety check: PassMIT
Release Processscragnog/HOT-Step-CPP174—~5.1kAutomated safety check: PassMIT

Similar skills

  • Change Documentation Writer

    jsmastery-pro/skills

    Writes PR descriptions, changelog entries, release notes and postmortems from the actual commits and diff, and saves each one in the right place.

    1.5k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevelopmentAuto-check: notes

  • GreptimeDB Release Runbook

    GreptimeTeam/greptimedb

    Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.

    6.7k GitHub stars~1.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Post Mortem

    hanamizuki/solopreneur

    Trace when a bug was introduced, find the root cause commit, understand why it happened, and produce a structured post-mortem report.

    152 GitHub stars~1.7k tokensUpdated 14 days ago
    DevOps & CloudAuto-check passed

  • AI Project Memory

    tudoumashu/ai-memory-skillpack

    Maintain bounded, durable AI project memory in a repository's docs/ai/ pack.

    456 GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Release Process

    scragnog/HOT-Step-CPP

    Runbook for cutting and publishing a HOT-Step CPP release via a v git tag that triggers the multi-platform CI build and drafts a GitHub Release.

    174 GitHub stars~5.1k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Handoff

    Mathews-Tom/armory

    Produces and refreshes .docs/handoff.md, a 200-line session-continuity runbook for coding agents.

    329 GitHub stars~1.7k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

More from ArabelaTso/Skills-4-SE

All 170 skills in this repo

  • Framework Migration Assistant

    ArabelaTso/Skills-4-SE

    Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).

    253 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Metamorphic Test Generator

    ArabelaTso/Skills-4-SE

    Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.

    253 GitHub stars~798 tokensUpdated 1 mo ago
    Auto-check passed

  • Reproduction Trace Instrumenter

    ArabelaTso/Skills-4-SE

    Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.

    253 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Spring Mvc To Boot Migrator

    ArabelaTso/Skills-4-SE

    Automatically migrate Spring MVC applications to Spring Boot.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

  • State Snapshot Instrumenter

    ArabelaTso/Skills-4-SE

    Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Bug History Summarizer

What does Bug History Summarizer do?

Summarizes the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing attempts, and regression history. Bug History Summarizer is an agent skill from ArabelaTso/Skills-4-SE. Summarizes the complete lifecycle of a bug across code versions, tracking its introduction, detection, fixing attempts, and regression history.

When should I use Bug History Summarizer?

Bug History Summarizer fits situations like: understand how a bug evolved over time; trace when and how a bug was introduced; analyze fix attempts and their effectiveness; identify regression patterns.

How do I install Bug History Summarizer in Claude Code?

Run `npx skills add ArabelaTso/Skills-4-SE --skill bug-history-summarizer -a claude-code`. Or copy the skill folder (skills/bug-history-summarizer in ArabelaTso/Skills-4-SE) into .claude/skills/bug-history-summarizer in your project. Claude Code loads it when a task matches its description.

How do I install Bug History Summarizer in Codex?

Run `npx skills add ArabelaTso/Skills-4-SE --skill bug-history-summarizer -a codex`. Or copy the skill folder (skills/bug-history-summarizer in ArabelaTso/Skills-4-SE) into .agents/skills/bug-history-summarizer in your project. Codex loads it when a task matches its description.

Can I use Bug History Summarizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ArabelaTso/Skills-4-SE --skill bug-history-summarizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-history-summarizer, .gemini/skills/bug-history-summarizer, .github/skills/bug-history-summarizer and .opencode/skills/bug-history-summarizer in your project.

What does Bug History Summarizer need to run?

Going by SKILL.md and its folder, Bug History Summarizer needs the command-line tools its instructions call (git).

Does Bug History Summarizer access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bug History Summarizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bug History Summarizer use?

Bug History Summarizer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bug History Summarizer use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bug History Summarizer?

Skills that share tags, products or a category with Bug History Summarizer: Change Documentation Writer (jsmastery-pro/skills, 1.5k stars), GreptimeDB Release Runbook (GreptimeTeam/greptimedb, 6.7k stars), Post Mortem (hanamizuki/solopreneur, 152 stars) and AI Project Memory (tudoumashu/ai-memory-skillpack, 456 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug History Summarizer?

ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 170 skills in this directory. The repository was last updated on August 21, 2026.

Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.