bug-bash-update

Updates BUG_BASH_GUIDE.md by analyzing git diffs and annotating bug fixes.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/cryptofish7/claude-skills --skill bug-bash-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-bash-update
Source: https://github.com/cryptofish7/claude-skills/tree/main/skills/bug-bash-update
Command: npx skills add https://github.com/cryptofish7/claude-skills --skill bug-bash-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating your bug bash documentation (docs/BUG_BASH_GUIDE.md) after development tasks, ensuring accurate tracking of features and bug fixes.

Core Features & Use Cases

  • Feature Tracking: Automatically adds new checklist items for implemented features.
  • Bug Fix Annotation: Updates existing bug entries with fix details and references.
  • Browser Verification: Confirms fixes in a live browser environment before marking them complete.
  • Use Case: After merging a pull request that fixes a critical bug, this Skill will find the corresponding bug entry in your guide, mark it as fixed with the PR reference, and attempt to verify the fix in the deployed application.

Quick Start

Run the bug-bash-update skill to update your bug bash guide with recent changes.

Frequently Asked Questions about bug-bash-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate bug bash documentation updates from git diffs?

Automate bug bash documentation updates by analyzing git diffs to append new feature checklist items and annotate bug fixes with PR references and verification status in BUG_BASH_GUIDE.md. This ensures accurate tracking of features and bug fixes after development tasks.

How does browser verification work for bug fixes in bug tracking documentation?

Browser verification for bug tracking documentation confirms fixes in a live browser environment before marking them complete. The process updates existing bug entries with fix details and attempts to verify the resolution in the deployed application.

Can I map specific file paths to documentation sections in a bug bash guide?

Yes, you can map file paths to specific documentation sections within BUG_BASH_GUIDE.md. This allows targeted updates so that changes in particular files automatically annotate their corresponding feature checklist items or bug entries.

What is the best way to track implemented features in a bug bash guide?

The best way to track implemented features is to automatically add new checklist items to your bug bash guide by analyzing git diffs. This maps recent development changes directly to the feature tracking documentation.

Do I need a deployed application to verify bug fixes in bug tracking documentation?

Yes, a deployed application is needed for browser verification of bug fixes. The process includes browser verification steps that confirm the resolution in a live environment before marking the bug entry as complete in the documentation.

Why does my bug bash guide not reflect recent git changes automatically?

Your bug bash guide does not reflect recent git changes automatically because it requires running an update process to analyze git diffs. This process maps file paths to specific documentation sections and annotates bug fixes with PR references and verification status.