Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

debugging

Étoiles213

Forks16

Mis à jour18 juin 2026 à 10:38

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

bearcove

bearcove/dodeca

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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

Debugging

When in doubt, add tracing:

C code: DBG() macro
Rust code: tracing::debug!() (not eprintln!)

IMPORTANT: Leave debug traces in place!

DO NOT remove DBG() calls from C code after debugging
DO NOT remove tracing::debug!() calls from Rust code after debugging
DO NOT run make clean in vendor/pikchr-c (it's disabled anyway)

Rationale

The C implementation is not used in production - debug traces are helpful for future investigations
Rust tracing can be turned on/off at compile time via RUST_LOG environment variable
Having traces in place makes future debugging much faster

Plus depuis ce dépôt

même dépôt

code-annotations

bearcove/dodeca

Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments.

2026-06-18213

codebase-layout

bearcove/dodeca

Codebase organization for pikru. Use when you need to find where specific functionality lives.

2026-06-18213

git-commands

bearcove/dodeca

Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.

2026-06-18213

idiomatic-rust

bearcove/dodeca

Idiomatic Rust patterns for pikru C port. Use when writing or reviewing Rust code ported from C. Don't write C in Rust - the goal is correct behavior, not line-by-line translation.

2026-06-18213

subtest-isolation

bearcove/dodeca

Create minimal subtests to isolate and fix complex bugs. Use when a test fails and the issue is buried in complexity.

2026-06-18213

testing

bearcove/dodeca

Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite.

2026-06-18213

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

Debugging

When in doubt, add tracing:

C code: DBG() macro
Rust code: tracing::debug!() (not eprintln!)

IMPORTANT: Leave debug traces in place!

DO NOT remove DBG() calls from C code after debugging
DO NOT remove tracing::debug!() calls from Rust code after debugging
DO NOT run make clean in vendor/pikchr-c (it's disabled anyway)

Rationale

The C implementation is not used in production - debug traces are helpful for future investigations
Rust tracing can be turned on/off at compile time via RUST_LOG environment variable
Having traces in place makes future debugging much faster