skills.rest
cofade
cofadeCOMMUNITY
Explore all skills by this author →
GitHub

debug-verbose

Instrument code execution flow with verbose logging to stdout.

16|2|Updated Jan 24, 2026
Search Tags:#code analysis#debugging#instrumentation#error identification#verbose logging
One-click install
npx skills add https://github.com/cofade/open-garden-planner --skill debug-verbose
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-verbose
Source: https://github.com/cofade/open-garden-planner/tree/main/.claude/skills/debug-verbose
Command: npx skills add https://github.com/cofade/open-garden-planner --skill debug-verbose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill addresses the challenges of debugging non-trivial bugs in code by providing targeted verbose instrumentation, aiding in understanding the actual runtime sequence and identifying root causes.

Core Features & Use Cases

  • Evidence-Based Debugging: Utilizes runtime logging to observe and understand the code's execution path.
  • Applicability: Ideal for asynchronous code, third-party frameworks, and unexpected behavior in the code.
  • Use Case: When encountering a non-obvious bug, apply this Skill to add logging statements and analyze the output for discrepancies between expected and actual behavior.

Quick Start

Use the debug-verbose skill to add verbose logging to the function 'process_orders', focusing on data validation and error handling.

Frequently Asked Questions about debug-verbose

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

FAQPage Schema
How do I debug asynchronous code with unexpected behavior?▼

Debug asynchronous code by implementing targeted verbose instrumentation to observe the actual runtime sequence. Outputting logs to stdout helps identify root causes and discrepancies in third-party frameworks.

What is the best way to identify root causes in non-trivial bugs?▼

Identify root causes using evidence-based debugging with runtime logging. By instrumenting the execution flow, you can observe the code's actual path and find discrepancies between expected and actual behavior.

Can I use Python logging module for runtime log output?▼

Yes, the Python logging module is required for runtime log output. It enables targeted verbose logging by instrumenting the execution flow and outputting logs to stdout for analysis.

When do I need verbose logging for code analysis?▼

You need verbose logging when encountering non-obvious bugs, debugging asynchronous code, or dealing with unexpected behavior in third-party frameworks. It provides evidence-based observation of the actual runtime sequence.

How to add logging statements to analyze execution flow discrepancies?▼

Add logging statements to target functions, focusing on data validation and error handling. This verbose instrumentation outputs the execution flow to stdout, allowing you to analyze discrepancies and identify issues.

Related Skills

Explore More Software Engineering Skills→
lobehublobehub
81.4k

debug

Create namespaced loggers with DEBUG, localStorage, or environment variable controls.

Official
Intermediate
acartineacartine
1

investigate

Trace runtime failures with file:line citations before proposing fixes.

Community
Advanced
igbuendigbuend
8

debug-mode-production-anti-pattern

Detect debug mode flags and endpoints in production configurations.

Community
Intermediate
devMoezdevMoez
1

node-inspect-debugger

Debug Node.js runtime failures via V8 inspector breakpoints and CDP.

Community
Intermediate