binding-audit

Audit alef-generated language bindings for missing Rust item exports.

91|16|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/kreuzberg-dev/alef --skill binding-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: binding-audit
Source: https://github.com/kreuzberg-dev/alef/tree/main/.ai-rulez/skills/binding-audit
Command: npx skills add https://github.com/kreuzberg-dev/alef --skill binding-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits alef-generated language bindings to find coverage gaps, so you can verify that every public Rust function and type is exposed across all enabled target languages.

Core Features & Use Cases

  • Config-canonical gap detection: Treats alef.toml exclusions and #[alef::skip], #[alef::exclude], #[alef::opaque] attributes as the source of truth to avoid false positives.
  • Cross-language binding comparison: Enumerates public Rust items, builds per-language exported sets, diffs them, and reports exactly which languages are missing each item.
  • Root-cause triage and upstream-ready outcomes: Determines whether a gap is caused by alef codegen, action/workflow scaffolding, or consuming configuration, then drives fixes with CHANGELOG.md updates and recorded SHAs/workflow URLs.

Quick Start

Use the binding-audit skill to audit the Rust library that you’re bound into multiple languages and produce a gap report that identifies missing exports and the most likely upstream cause.

Frequently Asked Questions about binding-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify every public Rust item is exposed across all language bindings?

Audit alef-generated language bindings by enumerating public Rust items, building per-language exported sets, and diffing them to report exactly which target languages are missing each function or type.

Why are some Rust public types missing in specific language bindings?

Missing types in specific language bindings occur when alef codegen, action scaffolding, or consumer configuration fails to expose items, which a cross-language diff identifies alongside an intentionality label and root-cause triage.

How do I check alef binding coverage without getting false positives for excluded items?

Canonical checking of alef.toml exclusions and #[alef::skip], #[alef::exclude], and #[alef::opaque] attributes treats intentional omissions as the source of truth, preventing false positive gaps in the binding coverage report.

When should I run a cross-language binding audit for my Rust crate?

Run a cross-language binding audit when preparing for a release, after adding new public APIs to a Rust crate, or when functions or types appear missing in specific enabled target languages.

How do I triage missing Rust exports to determine if the gap is in codegen or configuration?

Gap reporting triages missing Rust exports by routing fixes to alef codegen, action scripts, or consumer configuration, then drives resolutions with CHANGELOG.md updates and recorded SHAs or workflow URLs.

Does binding coverage auditing work with custom skip and opaque attributes in Rust?

Binding coverage auditing works with custom attributes by canonically checking #[alef::skip], #[alef::exclude], and #[alef::opaque] to verify that intentionally omitted public Rust items do not register as false coverage gaps.