Menu
Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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 | git-commands |
| description | Git command conventions for pikru. Use when running any git commands to avoid blocking on interactive pager. |
Always use --no-pager BEFORE the git command to avoid blocking on interactive pager:
git --no-pager log -10
git --no-pager diff
git --no-pager show
The --no-pager flag must come before the subcommand (log, diff, show, etc.), not after.