메뉴
Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments.
Codebase organization for pikru. Use when you need to find where specific functionality lives.
Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.
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.
Create minimal subtests to isolate and fix complex bugs. Use when a test fails and the issue is buried in complexity.
Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite.
| name | debugging |
| description | Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place. |
When in doubt, add tracing:
DBG() macrotracing::debug!() (not eprintln!)DBG() calls from C code after debuggingtracing::debug!() calls from Rust code after debuggingmake clean in vendor/pikchr-c (it's disabled anyway)RUST_LOG environment variable