Analyze browser evidence to locate bug root causes and impact scope.
npx skills add https://github.com/noni2she/agent-fix --skill bugfix-analyze
Please help me install this Agent Skill. Skill: bugfix-analyze Source: https://github.com/noni2she/agent-fix/tree/main/skills/bugfix-analyze Command: npx skills add https://github.com/noni2she/agent-fix --skill bugfix-analyze
Helps you precisely locate the root cause of a bug (including file/line), understand the impact scope, and choose the safest repair strategy without actually implementing the fix.
Use the bugfix-analyze skill when you have an issue JSON or an issue ID to generate a root-cause and impact analysis report for an engineer.
High-intent search queries and answers about installing and using this skill.
Root cause analysis for a reported bug combines browser reproduction evidence with static code inspection to pinpoint the exact file and line. It generates a structured RCA report explaining the failure and computing a confidence score.
Assessing the impact scope of a code bug involves analyzing shared and core component risks within the project context. This identifies impacted files and recommends whether a direct or tactical repair strategy is safest.
Generating a bug reproduction evidence package requires strict browser operations to collect objective signals like console errors, failed network requests, and DOM issues. This computes a reproduce confidence score for the RCA report.
Yes, standardized issue JSON containing expected and actual outcomes, reproduction steps, and module context supports automated impact assessment. The analysis outputs a structured RCA report with root cause location and fix-strategy recommendations.
Choose a tactical repair over a direct fix when the bug resides in shared or core components where direct changes carry high risk. The routing logic uses project context heuristics to recommend the safest repair approach.
A root cause analysis returns a need_more_info status when browser reproduction lacks objective signals or the issue JSON provides insufficient context. The final report requires enough evidence to confidently pinpoint the file and line.
drhazemibclcAnalyze bug reports to reproduce issues and classify them as bugs, user errors, or environmental problems.
linfordWuAutomates RCA from diagnostic logs, metrics, and traces into standardized fault reports.
soloamenteInspect DOM, console logs, network requests, and performance metrics via Chrome DevTools MCP.
uoyoCsharpDiagnose software bugs and apply targeted code fixes with regression impact notes.
