skills.rest
roborew
roborewCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugger

Analyze bug reports and logs to generate ranked root-cause hypotheses and fix plans.

Updated Jul 21, 2026
Search Tags:#planning#developer tools#code analysis#debugging#troubleshooting#bug fixing
One-click install
npx skills add https://github.com/roborew/opencode --skill debugger-roborew
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/roborew/opencode/tree/main/skills/debugger
Command: npx skills add https://github.com/roborew/opencode --skill debugger-roborew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of diagnosing software bugs and generating a structured plan to fix them, reducing the time spent on debugging and improving code quality.

Core Features & Use Cases

  • Root Cause Analysis: Identifies and ranks potential causes of bugs based on provided evidence.
  • Debug Planning: Creates a step-by-step plan for fixing the bug, including verification steps.
  • Use Case: When a critical bug is reported in production, this Skill can analyze logs and error reports to pinpoint the most likely cause and outline the exact steps needed for a fix.

Quick Start

Use the debugger skill to analyze the provided error logs and generate a debug plan.

Frequently Asked Questions about debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a debug plan from error logs and failing tests?▼

The debugger creates a diagnosis-first debug plan by analyzing bug reports, logs, and failing tests. It identifies the most likely causes and outlines exact verification steps needed to resolve the issue.

What is the best way to analyze a production bug report?▼

The debugger creates a diagnosis-first debug plan by analyzing bug reports, logs, and failing tests. It identifies the most likely causes and outlines exact verification steps needed to resolve the issue.

Can I use this to troubleshoot code analysis without specific artifact slugs?▼

No, generating a debug plan requires a specific artifact type and slug for plan generation. Without these specific inputs, the debugger cannot produce ranked root-cause hypotheses or a minimal fix strategy.

How do I pinpoint the root cause of a software bug from logs?▼

To pinpoint the root cause from logs, use a diagnosis-first approach that evaluates the evidence and ranks potential causes. This structured troubleshooting method highlights the most likely failure points.

When should I use an automated bug fixing plan instead of manual debugging?▼

Use an automated bug fixing plan when you have distinct artifact types and need to quickly reduce time spent on debugging. It structures the troubleshooting process to systematically improve code quality.

Related Skills

Explore More Software Engineering Skills→
Chulf58Chulf58

forge:debug

Run the FORGE debug pipeline to analyze bugs and generate fix plans.

Community
Advanced
RomualdPRomualdP

Systematic Debugging Process

Resolve software bugs via a ten-step workflow covering reproduction, root-cause analysis, minimal edits, and validation.

Community
Basic
kagent-devkagent-dev
3.5k

kagent-dev

Guide kagent development with CRD modifications, E2E testing, and PR workflows.

Official
Advanced
deflosjdeflosj

gstack-openclaw-investigate

Trace code paths from symptoms to root-cause hypotheses with regression tests.

Official
Advanced