skills.rest
alexandrbasis
alexandrbasisCOMMUNITY
Explore all skills by this author →
Website𝕏@alexandrbasisGitHub

dbg

Instrument code with targeted logging to analyze runtime execution evidence.

12|2|Updated Nov 20, 2025
Search Tags:#debugging#troubleshooting#logging#bug fixing#runtime#instrumentation
One-click install
npx skills add https://github.com/alexandrbasis/wythm-claude-workflows --skill dbg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dbg
Source: https://github.com/alexandrbasis/wythm-claude-workflows/tree/main/.claude/skills/dbg
Command: npx skills add https://github.com/alexandrbasis/wythm-claude-workflows --skill dbg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you find the root cause of bugs by systematically collecting runtime evidence and testing hypotheses, rather than guessing.

Core Features & Use Cases

  • Runtime Instrumentation: Inserts targeted logs into your code to capture execution flow and state.
  • Hypothesis Testing: Allows you to formulate and test specific theories about bug causes.
  • Evidence-Based Fixing: Ensures fixes are applied only after the root cause is confirmed by logs.
  • Use Case: When a user reports that a specific feature is crashing intermittently, you can use this Skill to instrument the relevant code sections, ask the user to trigger the feature, analyze the logs to pinpoint the exact line and condition causing the crash, and then apply a targeted fix.

Quick Start

Use the dbg skill to instrument the code and find the bug in the user-reported issue.

Frequently Asked Questions about dbg

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

FAQPage Schema
How do I debug intermittent application crashes instead of guessing the root cause?▼

Debug intermittent application crashes by instrumenting code with targeted logging to capture execution flow. You formulate hypotheses about the bug, reproduce the issue, and analyze runtime evidence to pinpoint the exact condition causing the failure.

What is the best way to troubleshoot runtime issues using code instrumentation?▼

Troubleshooting runtime issues with code instrumentation involves inserting precise log payloads into your code. This systematic workflow captures execution state, validates hypotheses about software defects, and ensures fixes are applied only after root causes are confirmed.

How do I find the root cause of a bug by testing hypotheses about software defects?▼

Find the root cause of a bug by generating specific hypotheses about software defects and instrumenting relevant code sections. Analyze the execution evidence from targeted logs to verify exactly which condition triggers the failure before applying a fix.

Can I use targeted logging to identify the exact line of code causing a crash?▼

Yes, targeted logging identifies the exact line of code causing a crash by capturing runtime execution flow and state. Instrument the relevant sections, trigger the feature, and analyze the log payloads to pinpoint the precise failure condition.

Does evidence-based bug fixing work for troubleshooting intermittent application failures?▼

Evidence-based bug fixing works for troubleshooting intermittent application failures by systematically collecting runtime evidence. Insert targeted logs, ask users to trigger the feature, and analyze the execution data to validate your hypotheses about the defect.

What are the limitations of using runtime instrumentation for bug fixing?▼

Runtime instrumentation for bug fixing requires precise log payload structure and a systematic workflow for hypothesis generation, reproduction, analysis, and verification. It is limited by the need to accurately reproduce the intermittent issue to capture valid execution evidence.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
OiAnthonyOiAnthony
8

hunt

Diagnose root causes of errors, crashes, and regressions using repro steps and source traces.

Community
Advanced
kmshihab7878kmshihab7878
6

production-monitoring

Monitor containerized Python services on AWS EKS with Grafana, Prometheus, Loki, and OpenTelemetry.

Community
Advanced
d-o-hubd-o-hub
11

rust-code-quality

Review Rust code quality across eight dimensions including async patterns and error handling.

Community
Advanced