Diagnose root causes of errors, crashes, regressions, and failing tests before fixes.
npx skills add https://github.com/redisread/product-stories --skill hunt-redisread
Please help me install this Agent Skill. Skill: hunt Source: https://github.com/redisread/product-stories/tree/main/.agents/skills/hunt Command: npx skills add https://github.com/redisread/product-stories --skill hunt-redisread
Applying quick fixes to bugs often masks the underlying root cause, leading to recurring issues, new defects, and wasted debugging time. This Skill eliminates that risk by enforcing root cause identification before any code changes are made.
Use the hunt skill to identify the root cause of the error reported in your latest failing test before applying any fix.
High-intent search queries and answers about installing and using this skill.
To diagnose the root cause of a failing test, you need to form a hypothesis, gather runtime evidence, and validate reproducibility before changing code. This ensures your fix addresses the underlying defect rather than just masking the symptom.
The best way to find a regression after a dependency update is to bisect commits to identify the exact change that introduced the breakage. This systematic regression diagnosis prevents guessing and targets the true root cause.
Yes, systematic bug hunting supports intermittent runtime issues and visual rendering bugs. It provides specialized debug modes with targeted checklists and evidence requirements for visual defects, IME issues, and native app freezes.
Applying a quick fix leads to recurring issues because it masks the underlying root cause without resolving it. Enforcing root cause identification before any code changes eliminates the risk of new defects and wasted debugging time.
Yes, root cause analysis works for screenshot-reported defects across web, native, and CLI applications. It enforces hypothesis validation and blast radius checks to ensure fixes address the actual visual rendering problem.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
robkamEnforce a red-green-proof loop starting with a failing regression test.
DaddyElonMusk69Identify software bug root causes using a four-phase debugging process.
ilove323Diagnose software failures and generate a structured debugging report.
