bug-resolver
CommunityDiagnose frontend bugs in-browser and fix them.
System Documentation
What problem does it solve?
Orchestrator skill for diagnosing and fixing frontend bugs. Uses Chrome DevTools MCP to inspect the live page — console errors, failed network requests, DOM state, visual glitches — then traces the root cause to code, fixes it, and verifies the fix via DevTools. Manages a bug state file for complex bugs. Routes to appropriate QA skills for regression verification after fix. Use this skill when the user reports a runtime bug with a URL, shares an error screenshot, pastes a console error, says "this is broken," "why isn't this working," "debug this page," or shares a bug ticket. Also trigger when the user shares a screenshot of a broken page. The key difference from feature-updater's bug fix path: this skill starts in the BROWSER to diagnose, then moves to CODE to fix.
Core Features & Use Cases
- Browser-first diagnosis and evidence collection (console, network, DOM)
- Bug state file management and routing to QA regression verification
- Guided hand-off to code repair steps via subskills like code-reviewer and testing-strategy
Quick Start
Reproduce the bug in the browser and capture console, network, and DOM evidence for verification.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: bug-resolver Download link: https://github.com/Nikhil-Chopra-7/claude-frontend-skills/archive/main.zip#bug-resolver Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.