api-contract-reviewerlisted

# API Contract Reviewer Reviews **contracts** — REST OpenAPI specs and protobuf `.proto` files — for stability, versioning hygiene, and completeness. Catches the contract issues architects encoded rules against before they ship to clients. ## 1. When to invoke - A PR changes `.proto` files, OpenAPI YAML, or any handler that affects the wire contract. - Before publishing a new major version of an API. - Before deprecating a field or method. - Periodic audit of an existing API for drift between spec and implementation. ## 2. Output format Same shape as [security-reviewer §2](../security-reviewer/SKILL.md#2-output-format) — findings table with severity, then a one-line summary. ```markdown | Severity | Rule | Location | Evidence | Fix | |---|---|---|---|---| | Critical | Breaking change to v1 | `proto/orders/v1/order.proto:23` | Field `status` type changed `string` → `int32` | Revert; introduce `status_v2` as a new field in v1, deprecate `status`, or bump to v2 | | High | Versioning mismatch | `openapi.yaml` | Endpoint `/orders` lacks `/v1/` prefix | Add `/v1/` prefix per rest-api-architect §4 | | Medium | Missing OpenAPI example | `openapi.yaml:42` | `CreateOrderRequest` has no `example:` | Add a realistic example — drives SDK gen + docs | | Low | Inconsistent error shape | `openapi.yaml` | 404 returns `{detail: ...}` while 422 returns RFC 7807 | Standardize on RFC 7807 per rest-api-architect §7 | ``` Severity guide: - **Critical** — wire-breaking change in a stable ver