cpp-api-abi-review

Installation
SKILL.md

C++ API And ABI Review

Use this skill when C++ code defines or changes a library boundary that other code compiles or links against: public headers, exported classes and functions, shared-library interfaces, or plugin ABIs.

The goal is to make every boundary contract explicit: what is API (source compatibility), what is ABI (binary compatibility), which changes break each, and how the library versions and communicates those breaks.

UTILITY SKILL. INVOKES: read-only file access for supplied targets; no other tools or skills. FOR SINGLE OPERATIONS: use for focused header review, ABI-impact analysis of a change, boundary design, or compatibility policy questions.

Scope

  • Use this skill for public header hygiene, ABI stability analysis of class/function changes, ODR risk, noexcept as an API contract, inline functions and templates crossing library boundaries, default arguments vs overloads, pimpl and other compilation-firewall idioms, symbol visibility and export macros, extern "C" boundaries, and versioned/inline namespaces.
  • Apply it to diffs against installed/public headers, new public APIs, plugin interfaces, and questions like "can I change this without breaking downstream binaries?".
  • Distinguish three compatibility levels in every answer: source (API), binary (ABI), and semantic (behavioral contract).

DO NOT USE FOR:

  • Internal refactors with no exported or installed surface; build-system mechanics; packaging/distribution policy.
  • General API ergonomics or naming review with no compatibility, ODR, or boundary question.
Installs
1
GitHub Stars
2
First Seen
10 days ago