Systematic Debugging
Skill Verified ActiveUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
To ensure bugs, test failures, and unexpected behaviors are addressed systematically by finding the root cause before proposing any solutions.
Features
- Mandates root cause investigation before fixes
- Provides a 4-phase debugging process
- Identifies and prevents common debugging shortcuts
- Guides investigation in multi-component systems
- Supports finding the original trigger of errors
Use Cases
- Use for any bug, test failure, or unexpected behavior
- Use when under time pressure to avoid guessing
- Use when previous fixes haven't worked
- Use when the issue is not fully understood
Non-Goals
- Proposing fixes without root cause investigation
- Quickly patching symptoms
- Skipping debugging steps due to time constraints
- Making multiple changes at once
Installation
First, add the marketplace
/plugin marketplace add obra/superpowers/plugin install superpowers@superpowers-devQuality Score
VerifiedTrust Signals
Similar Extensions
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Playwright Best Practices
100Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
Troubleshooting
100Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Root Cause Tracing
99Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior