superpowers-systematic-debuggingEnforce a four-phase debugging process—root cause investigation, pattern analysis, hypothesis testing, and evidence-based fix verification—for all bugs and f...
Install via ClawdBot CLI:
clawdbot install axelhu/superpowers-systematic-debuggingGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 9, 2026
A developer encounters a critical defect in production code. Using the systematic debugging process, they avoid common pitfalls like guessing fixes and instead conduct a thorough root cause analysis before implementing a verified solution.
An QA engineer faces recurring test failures in a CI pipeline. The skill guides them to stabilize reproduction, identify pattern differences, and apply targeted fixes rather than patching symptoms.
A system administrator diagnoses unexpected performance degradation. They follow the structured approach to examine recent changes, trace data flow, and implement a single evidence-based fix that resolves the root cause.
When two services fail to communicate correctly, an integration engineer uses the debugging protocol to isolate the issue, compare working vs broken endpoints, and deploy a minimal correction.
Offer systematic debugging as a premium consulting engagement for tech teams facing persistent, complex bugs. Revenue is generated per engagement or retainer.
Provide structured training programs and workshops to teach the systematic debugging methodology to engineering teams. Revenue comes from course fees and corporate training packages.
Integrate the debugging workflow into an existing development platform or CI/CD tool as a plugin or extension. Revenue from subscription fees or freemium model.
💬 Integration Tip
Start by training your team on the four-phase process using real bugs; then incorporate it into code review and incident response checklists.
Scored May 9, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.