Skip to content
Back to skills

Code Annotations

ASecurity

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

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 8, 2026
documentationrust

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill code-annotations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Annotations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Annotations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-code-annotations/badge)](https://www.skillsdirectory.com/skills/majiayu000-code-annotations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-annotations
description: Code annotation requirements for pikru. Use when writing or porting Rust functions from C code. All ported functions must have cref comments.
---

# Code Annotations

All Rust functions ported from C must be annotated with a cref comment:

```rust
// cref: c_function_name
fn rust_function() { ... }
```

## Purpose

The `// cref:` comments create a traceable link between the Rust implementation and the original C function it was ported from. This helps:

- Future maintainers understand the origin of the code
- Cross-reference behavior between C and Rust implementations
- Debug discrepancies between the two implementations

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.