skills.rest
Srujan0798
Srujan0798COMMUNITY
Explore all skills by this author →
GitHub

bug-hunt

Diagnose software bugs by reproducing failures and tracing root causes.

Updated Apr 18, 2026
Search Tags:#debugging#protocol#reproduction#root-cause-analysis#stack-trace#bug-triage
One-click install
npx skills add https://github.com/Srujan0798/NRG --skill bug-hunt-srujan0798
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-hunt
Source: https://github.com/Srujan0798/NRG/tree/main/.claude/skills/bug-hunt
Command: npx skills add https://github.com/Srujan0798/NRG --skill bug-hunt-srujan0798

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug diagnosis and root cause analysis for software failures, guiding engineers to reproduce, trace, and fix issues without guessing.

Core Features & Use Cases

  • Reproduce failures using a defined protocol to capture exact error messages and stack traces.
  • Systematically trace the error path to identify root causes across functions and modules.
  • Prepare a structured fix protocol and documentation to prevent recurrence.

Quick Start

Reproduce the bug locally using the provided commands, then follow the protocol to trace and identify the root cause.

Frequently Asked Questions about bug-hunt

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

FAQPage Schema
How do I perform root-cause analysis for a runtime exception using a stack trace?▼

Root-cause analysis for a runtime exception requires a protocol-driven workflow that reproduces the failure, traces the error path across modules using the stack trace, and identifies the underlying cause without guessing.

What is the best way to systematically reproduce flaky bugs in my codebase?▼

To systematically reproduce flaky bugs, you need a defined reproduction protocol that captures exact error messages and stack traces by executing specific local commands to reliably trigger the intermittent failure.

How do I trace an error path across functions and modules after reproducing a test failure?▼

Tracing an error path after a test failure involves systematically following the stack trace across functions and modules to pinpoint where the failure originates, applying a structured bug triage process.

Can I use a bug triage protocol for diagnosing issues without automatically applying a code fix?▼

Yes, a bug triage protocol can guide you through reproducing failures, tracing error paths, and preparing a structured fix protocol without automatically performing the code fix itself.

Do I need reproducible steps and error traces available before starting bug diagnosis?▼

Yes, bug diagnosis requires reproducible steps and error traces to be available in your codebase so the protocol can accurately trace the error path and perform a reliable root-cause analysis.

Related Skills

Explore More Software Engineering Skills→
Space-DinosaursSpace-Dinosaurs
12

agent-debugger

Diagnose root causes of failing tests and stack traces from codebase inspection.

Official
Advanced
a29paula29paul
1

gstack-openclaw-investigate

Enforce root cause investigation before bug fixes in software debugging workflows.

Community
Advanced
vstorm-covstorm-co
1.0k

systematic-debugging

Diagnose and fix software errors using a structured five-step debugging loop.

Official
Intermediate
k97k97
4

firebase-crashlytics

Integrate Firebase Crashlytics into Android and iOS apps for crash reporting.

Community
Intermediate