Skip to content
Back to skills

Ovstorage Contributor Regenerate C Headers

ASecurity

Use when Rust changes affect the ovstorage plugin ABI header and the checked-in generated copies must be refreshed.

  • 15 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 19, 2026
ai-agentsrustgoc++bashapi

Works with

  • api

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add NVIDIA-Omniverse/ovstorage --skill ovstorage-contributor-regenerate-c-headers --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ovstorage Contributor Regenerate C Headers?

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

Security grade badge for Ovstorage Contributor Regenerate C Headers
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvidia-omniverse-ovstorage-contributor-regenerate-c-headers/badge)](https://www.skillsdirectory.com/skills/nvidia-omniverse-ovstorage-contributor-regenerate-c-headers)

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: ovstorage-contributor-regenerate-c-headers
description: Use when Rust changes affect the ovstorage plugin ABI header and the checked-in generated copies must be refreshed.
license: CC-BY-4.0
version: "0.1.0"
author: NVIDIA Omniverse
tags: [ovstorage, c-abi, headers]
tools: [Read, Bash]
compatibility: Requires an ovstorage checkout and the Rust toolchain used by make regenerate-headers.
---

# Regenerate C Headers

## Goal

Keep the checked-in copies of the plugin ABI header synchronized with the
Rust source they are generated from.

## Scope

Only `ovstorage_plugin.h` is generated, from the `ovstorage-plugin` crate.
It has to be: plugins are prebuilt cdylibs loaded at runtime, so host and
plugin compile separately and must agree on struct layout.

`ovstorage.h` is NOT generated. The C application API ships as source, so
consumers compile that header together with the implementation it declares
and there is no binary boundary to freeze. Edit it directly, alongside
`ovstorage-c-source/src`; the link-completeness gate in
`make c-source-examples` is what holds the two in agreement.

## Recipe

1. Make the ABI-affecting Rust change under `ovstorage-core/ovstorage-plugin`.
2. Run `make regenerate-headers`.
3. Inspect the diff under
   [`ovstorage-plugin/include`](../../ovstorage-core/ovstorage-plugin/include/)
   and its copy in
   [`ovstorage-c-source/include`](../../ovstorage-c-source/include/).
4. Run `make verify-headers-clean`.
5. Commit the Rust source and regenerated headers together.

## References

- [C/C++ source distribution](../../ovstorage-c-source/README.md) for
  C ABI stability rules.

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.