Debug
ChatGPT pluginDiagnose and fix bugs
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools389th of 537 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 386 | #4991 | — | |
| 387 | #4992 | — | |
| 388 | #4993 | — | |
| 389 | #4997 | — | |
| 390 | #4999 | — | |
| 391 | #5002 | — | |
| 392 | #5009 | — |
Find the root cause of broken behavior, reproduce it, fix it with regression coverage, and use browser or performance diagnostics when evidence requires them.
Example prompts
- “Diagnose this regression and fix the root cause”
- “Find why this browser flow is failing”
- “Resolve this bug with a regression test”
Skills
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
debugging-and-error-recovery
Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
entry-debug
Use whenever the Debug plugin is selected. Route the request to the intended bundled workflow while keeping all dependencies internal to this plugin.
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
- Categories
- Made by
- Saul Martí
- Sign-in
- On Install
- Capabilities
- Diagnose and fix bugs
- Availability
- Available
- Version
- 2.0.0
- Keywords
- engineering-suite, debug, skills
- Created
- September 10, 2026