Menu
Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite.
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.
Basé sur la classification professionnelle 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.
Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug traces in place.
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.
| name | testing |
| description | Testing conventions for pikru. Use when running tests to avoid timeouts. DO NOT run the full test suite. |
DO NOT run the full test suite with cargo test - it times out and hangs.
Run specific tests only:
cargo test test01 -- --nocapture
cargo test test12 -- --nocapture
Never try to count/grep test results from the full suite - it will hang.
The pikru test suite runs pikchr rendering comparisons which can be slow. Running all tests at once exceeds reasonable timeout limits.