Embed DBG() and tracing::debug!() trace calls in C and Rust code.
npx skills add https://github.com/bearcove/pikru --skill debugging-bearcove
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
Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.
Enable tracing in your builds and insert DBG() or tracing::debug!() calls to surface useful debug information.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
DexploarerConfigure distributed tracing with Jaeger, Zipkin, or Datadog for microservices.
thechandanbhagatAnalyze stack traces and logs to identify root causes and suggest fixes.
multicamImplement printf-style debug logging with DEBUG_LOG macros in C programs.
mgreenlyProvide printf-style debug logging for C projects with release-build disabling.
