axodus-debuggingDiagnose failures using reproduce → isolate → fix → verify workflow.
Install via ClawdBot CLI:
clawdbot install mzfshark/axodus-debuggingGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 21, 2026
CI pipeline detects failing tests in a Red Hat deployment. The debugger skill systematically reproduces the failure, isolates the smallest failing unit, and identifies root cause (e.g., API version mismatch). Fix is applied and verified, reducing manual debugging time by 70%.
A critical service crashes with a null pointer exception in production. Using logs and reproduction steps, the skill localizes the issue to a missing null check after a recent code change. The fix is deployed and verified with regression tests, ensuring no recurrence.
A Red Hat-based application experiences 30% slower response times after an update. The skill reproduces the performance issue, isolates it to a new database query, and proposes an optimized index or query rewrite. Verification shows restored performance without side effects.
A custom Red Hat deployment fails to start due to a misconfigured environment variable. The skill uses the provided environment object to reproduce the error, identifies the incorrect variable, and corrects it. Verified by successful startup and same-configuration tests.
Offer automated debugging for CI/CD pipelines on a per-incident or subscription basis. Teams submit symptoms and logs, receive structured root cause analysis and fixes.
Integrate the debugger skill into existing Site Reliability Engineering (SRE) tools. Provide as an add-on for platforms like Red Hat OpenShift or Ansible, charging per CPU core or cluster.
Package the skill with other developer tools (code review, testing) as a suite. Offer to enterprises to reduce time-to-resolve production issues, with tiered pricing based on number of developers.
💬 Integration Tip
Integrate with your CI/CD pipeline by capturing failing test output and logs as inputs; the skill outputs structured data that can feed into tracking systems like Jira.
Scored May 21, 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.