Debug full-stack apps via 5 Whys, Vitest, Biome, and agent-browser.
npx skills add https://github.com/GrupoUS/gpus --skill debug-grupous
Please help me install this Agent Skill. Skill: debug Source: https://github.com/GrupoUS/gpus/tree/main/.kilocode/skills/debug Command: npx skills add https://github.com/GrupoUS/gpus --skill debug-grupous
This Skill provides a unified approach to identifying, diagnosing, and resolving bugs across backend, database, and frontend applications, streamlining the development and maintenance process.
biome for linting/type checking and vitest for unit and integration tests.agent-browser for visual debugging, element interaction, and end-to-end testing.Use the debug skill to run backend checks and tests for the current project.
High-intent search queries and answers about installing and using this skill.
Systematic debugging involves a 4-phase process: Reproduce, Isolate, Understand, and Fix. After reproducing the bug, you isolate the faulty code, perform root cause analysis using the 5 Whys technique, and verify the fix through automated testing.
To find the root cause of a database bug, leverage Neon MCP tools to identify slow queries and execute SQL. This isolates problematic database operations and pinpoints performance bottlenecks or faulty data logic within your application.
Yes, you can use Vitest and Biome for automated testing when fixing code errors. Vitest executes unit and integration tests, while Biome performs linting and type checking to verify that your code fixes are valid and structurally sound.
Yes, this debugging framework works with Railway deployment logs and agent-browser. It provides commands to inspect Railway logs for deployment errors and utilizes agent-browser for visual debugging, element interaction, and end-to-end frontend testing.
To systematically reproduce and isolate a reported bug, follow a structured debugging process to recreate the exact issue, then narrow down the specific faulty code area. This isolation step is critical before performing root cause analysis with the 5 Whys technique.
The 5 Whys technique for root cause analysis is limited by the investigator's domain knowledge and may stop prematurely at a symptom. It is most effective when combined with automated testing and database query analysis to empirically verify the identified root cause.
mcauduro0Test local web applications with Playwright scripts and capture screenshots.
mchien15Automate browser-based testing with Playwright, Vitest, and k6.
LaunchPadLabMonitor Render service health, performance metrics, logs, and PostgreSQL databases.
Chang-Shih-YungGenerate time-limited setup keys to share local browser sessions with remote AI agents.