skills.rest
berrzebb
berrzebbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

role:debugger

Debugs code by tracking bugs, analyzing root causes, and suggesting fixes.

22|7|Updated Feb 23, 2026
Search Tags:#code analysis#debugging#troubleshooting#root cause analysis#error resolution#bug tracking
One-click install
npx skills add https://github.com/berrzebb/SoulFlow-Orchestrator --skill role-debugger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: role:debugger
Source: https://github.com/berrzebb/SoulFlow-Orchestrator/tree/main/src/skills/roles/debugger
Command: npx skills add https://github.com/berrzebb/SoulFlow-Orchestrator --skill role-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and fix bugs in code by systematically tracing errors, analyzing their root causes, and proposing solutions.

Core Features & Use Cases

  • Bug Tracking: Pinpoints the source of errors within codebases.
  • Root Cause Analysis (RCA): Performs in-depth analysis to find the fundamental reason for a bug, not just the symptom.
  • Solution Proposal: Suggests specific code modifications to resolve identified issues.
  • Use Case: When a critical bug is reported in production, this Skill can be invoked to analyze the error logs, reproduce the issue, identify the faulty code section, and suggest a fix.

Quick Start

Use the debugger skill to analyze the error reported in the logs and suggest a fix.

Frequently Asked Questions about role:debugger

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

FAQPage Schema
How do I find the root cause of a bug in my code?▼

Root cause analysis traces errors systematically to pinpoint the fundamental reason for a bug rather than just addressing the symptom. It analyzes error logs, reproduces the issue, and identifies the faulty code section to propose targeted fixes.

Can I use hypothesis-driven debugging to track down code errors?▼

Hypothesis-driven debugging requires generating at least three hypotheses before modifying any code. It strictly validates these assumptions through falsification tests, ensuring accurate bug tracking and preventing ineffective patching.

How do I analyze error logs to reproduce and fix a critical bug?▼

Analyzing error logs allows you to reproduce the reported issue and trace the execution path. This in-depth code analysis identifies the exact source of the error within the codebase, enabling the proposal of specific code modifications.

Why does my code fail and how can I systematically resolve the error?▼

Systematic error resolution involves tracking the bug to its origin and performing root cause analysis. By identifying the fundamental reason for the failure, targeted code modifications can be suggested to fully resolve the issue.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
mgd34msumgd34msu
6

debugging

A debugging tool for diagnosing and resolving software defects in your codebase, featuring automated workflows for locating errors and generating corrected code.

Community
Advanced
SethyPagnaSethyPagna

python-debugpy

Attach interactive debuggers to Python processes for breakpoint-driven tracing.

Community
Advanced