bug-hunt

Execute repros and create failing tests to verify bugs in codebases.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/skylarsabo/code-ops --skill bug-hunt-skylarsabo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-hunt
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/rigor/skills/bug-hunt
Command: npx skills add https://github.com/skylarsabo/code-ops --skill bug-hunt-skylarsabo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill focuses on identifying and verifying real bugs with failing tests, ensuring that each candidate bug is proven before reporting.

Core Features & Use Cases

  • Verification-First Methodology: Each bug candidate is proven with a failing test before being reported.
  • Audit Mode: Reads and executes repros without making source fixes.
  • Tiered Findings: Findings are categorized into CONFIRMED, PROBABLE, and SPECULATIVE.
  • Root Cause Analysis: Identifies the root cause of each confirmed bug and searches for related siblings in the codebase.

Quick Start

Run /rigor:bug-hunt to initiate the bug hunting process for the current codebase.

Frequently Asked Questions about bug-hunt

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

FAQPage Schema
How do I verify suspected codebase bugs with failing tests instead of just making guesses?

Bug hunting verifies suspected codebase bugs by executing repros and creating failing tests. It uses a verification-first methodology to prove each candidate bug before reporting it, ensuring accurate and actionable findings.

What is the best way to perform a security testing and codebase audit without modifying source code?

Security testing and codebase audits can run in audit mode, which reads and executes repros without making source fixes. This allows you to identify vulnerabilities and verify bugs while keeping the original code intact.

How does root cause analysis work when debugging software to find related sibling bugs?

Root cause analysis identifies the origin of each confirmed bug during debugging and then searches the codebase for related sibling issues. This ensures comprehensive verification and detection of similar defects across the project.

Can I categorize bug hunting findings by confidence levels like confirmed or speculative?

Yes, bug hunting categorizes findings into tiered confidence levels: CONFIRMED, PROBABLE, and SPECULATIVE. This classification helps prioritize debugging efforts based on the verification strength of each detected issue.

Do I need specific dependencies or frameworks to run repro tests for bug verification?

No specific dependencies are required to run repro tests for bug verification. The skill operates independently using its internal scripts to execute repros and validate candidate bugs against your current codebase.