debugging

Name: debugging
Availability: InStock
Author: bearcove

Embed DBG() and tracing::debug!() trace calls in C and Rust code.

29|4|Updated Dec 2, 2025

Search Tags:#debugging #rust #tracing #c #coding-conventions #pikru #debug-macros

Ready to run

npx skills add https://github.com/bearcove/pikru --skill debugging-bearcove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/bearcove/pikru/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/bearcove/pikru --skill debugging-bearcove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.

Core Features & Use Cases

C code: DBG() macro
Rust code: tracing::debug!() (not eprintln!)
IMPORTANT: Leave debug traces in place and avoid removing them during debugging

Quick Start

Enable tracing in your builds and insert DBG() or tracing::debug!() calls to surface useful debug information.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I keep debug traces in place when investigating issues in C and Rust?▼

To keep debug traces in place during issue investigation, use the DBG() macro in C code and tracing::debug!() in Rust, avoiding their removal or disabling throughout the debugging process.

What is the correct macro for adding Rust debug traces instead of eprintln?▼

The correct method for adding Rust debug traces is tracing::debug!(), which should be used instead of eprintln to ensure consistent debugging practices and maintain trace visibility.

Should I remove vendor debug traces when fixing bugs in the codebase?▼

You should not remove vendor debug traces when fixing bugs; the guidance explicitly advises leaving existing debug traces intact and avoiding their removal during debugging investigations.

How do I enable tracing to surface debug information during development?▼

To enable tracing during development, activate tracing in your builds and insert DBG() calls in C or tracing::debug!() calls in Rust to surface useful debug information for issue investigation.

Why does leaving debug traces in code help with faster debugging?▼

Leaving debug traces in code helps with faster debugging by ensuring consistent visibility into application behavior, allowing developers to rely on existing DBG() and tracing::debug!() calls during investigations.