Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

debugging

Sterne213

Forks16

Aktualisiert18. Juni 2026 um 10:38

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

bearcove

bearcove/dodeca

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·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

Mehr aus diesem Repository

gleiches Repository

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