bh

Coordinate a six-category bug scan with five-judge verification and batch fixes.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/deedeeharris/bug-hunter-plugin --skill bh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bh
Source: https://github.com/deedeeharris/bug-hunter-plugin/tree/main
Command: npx skills add https://github.com/deedeeharris/bug-hunter-plugin --skill bh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end bug-hunting process by coordinating a rigorous, babysitter-driven workflow that scans, verifies, deduplicates, proves, fixes in batches, runs regression checks, and re-scans until the repository is clean.

Core Features & Use Cases

  • End-to-end bug-hunting workflow orchestrated by Babysitter across 6 bug categories.
  • 5-judge verification with evidence and scoring to filter false positives.
  • Fix in batches with convergence scoring, regression checks, hard build and test gates, and scoped re-scan of modified files.
  • Modes include YOLO (auto-fix) and Interactive (breakpoints before fixes and commits) to balance automation and control.

Quick Start

Invoke /bh to launch the generic bug-hunter babysitter process on the current repository.

Frequently Asked Questions about bh

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

FAQPage Schema
How do I automate end-to-end bug hunting in my repository?

Automated bug hunting coordinates a 6-category scan, 5-judge verification, deduplication, proof, batch fixes, regression checks, and committed re-scans until the codebase is clean. Invoke /bh to launch the orchestration process on the current repository.

How does the 5-judge verification mechanism work for code quality scans?

The 5-judge verification mechanism evaluates scanned bugs with evidence and automated confidence scoring to filter false positives. It ensures only verified issues proceed to batch fixes, maintaining strict quality guardrails throughout the bug-hunting workflow.

Can I run automated bug fixing in YOLO mode for DevOps workflow automation?

Yes, YOLO mode enables auto-fix automation for DevOps teams. Alternatively, Interactive mode inserts breakpoints before fixes and commits, allowing you to balance full automation with manual control over the regression and re-scan convergence process.

What is the best way to handle deduplication and proof during bug fixing?

The best way is an orchestrated workflow that automatically deduplicates verified bugs and generates proof before applying batch fixes. This process repeats with scoped re-scans of modified files, running hard build and test gates until convergence scoring shows the codebase is clean.

Does this automated bug hunting workflow require Babysitter orchestration to function?

Yes, Babysitter orchestration is required to manage cross-task coordination across the 6-category scan, 5-judge verification, batch fixes, regression checks, and re-scans. It provides the guardrails and convergence scoring needed for a clean codebase.

What are the limitations of interactive mode for code quality regression checks?

Interactive mode requires manual intervention at breakpoints before fixes and commits, which slows down the bug-hunting workflow compared to YOLO auto-fix mode. However, it provides tighter control over regression checks and batch fix convergence scoring.