skills.rest
boshu2
boshu2COMMUNITY
Explore all skills by this author →
WebsiteGitHub

bug-hunt

Investigate bugs systematically and generate reproducible root-cause reports.

418|40|Updated Nov 5, 2025
Search Tags:#git#debugging#root-cause#archaeology#issue-tracking#bug#bug-report
One-click install
npx skills add https://github.com/boshu2/agentops --skill bug-hunt-boshu2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-hunt
Source: https://github.com/boshu2/agentops/tree/main/skills/bug-hunt
Command: npx skills add https://github.com/boshu2/agentops --skill bug-hunt-boshu2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires beads.

What problem does it solve?

This Skill helps software teams systematically investigate bugs and produce reproducible root-cause reports.

Core Features & Use Cases

  • Phase-driven investigation: Guides root-cause discovery, pattern analysis, hypothesis testing, and implementation planning.
  • Git archaeology: Provides commands and steps to trace changes, blame, and historical context.
  • Issue-tracking integration: Outputs findings to .agents/research/ for documentation and collaboration.
  • Use Case: When a bug is reported, run the skill with a symptom to generate a bug report, failure tracking, and a clear fix plan.

Quick Start

Run /bug-hunt <symptom> to start a structured investigation and store results under .agents/research/.

Frequently Asked Questions about bug-hunt

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

FAQPage Schema
How do I conduct a systematic bug investigation using git archaeology?▼

Systematic bug investigation using git archaeology involves tracing changes, blame, and historical context to discover root causes. This skill guides you through pattern analysis, hypothesis testing, and a 4-phase workflow to produce reproducible bug reports and fix plans.

What is the best way to trace a bug's root cause across a codebase?▼

Tracing a bug's root cause is best done through a structured 4-phase workflow: discovery, pattern analysis, hypothesis testing, and implementation planning. This approach uses git archaeology to trace historical changes and outputs reproducible reports under .agents/research.

How do I create a reproducible bug report from a codebase symptom?▼

To create a reproducible bug report, run the skill with a reported symptom to generate structured results. It conducts root-cause discovery and hypothesis testing, storing the reproducible failure tracking data and clear fix plan under .agents/research.

Do I need beads issue-tracking to perform root-cause analysis?▼

Yes, beads is required as a dependency for issue-tracking integration. The skill uses beads to satisfy reproducibility and traceability requirements, outputting structured investigation findings to .agents/research for documentation and collaboration.

How does git archaeology help with debugging complex issues?▼

Git archaeology helps with debugging complex issues by providing commands and steps to trace historical code changes, blame specific lines, and gather context. This historical analysis feeds into the 4-phase workflow for robust fixes across codebases.

Related Skills

Explore More Software Engineering Skills→
cameronraysmithcameronraysmith
14

issues-beads-init

Initialize beads issue tracking with dolt database persistence for new repositories.

Community
Intermediate
rednam-ntnrednam-ntn

vibe-debugger

Diagnose software bugs, generate BUG_REPORT.md, and implement verified fixes.

Community
Advanced
ethicalcapitalethicalcapital

beads-issue-tracking

Synchronize issue tracking across GitHub, Linear, and Forgejo using Beads.

Official
Advanced
sd0xdevsd0xdev
187

git-investigate

Trace code authors, changes, and root causes using git history commands.

Community
Basic