bug-history-summarizer

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