Pact Coverage

Analyses Pact v2/v3/v4 interactions against an OpenAPI spec and reports gaps across four core dimensions: path/method, status codes, request body required fields, and response body required fields. An optional fifth dimension — consumer code status branch analysis — surfaces status codes the consumer handles in code but hasn't tested in any pact. Never modifies files.

When the spec is an AsyncAPI 3.x document the same skill measures Pact message pacts instead; see AsyncAPI mode.

Prerequisites: ripwire is required — as an MCP server for interactive use (see ripwire MCP setup above), or as a CLI binary for CI scripts (see Scripts (CI / advanced) below). Run command -v ripwire to check; see references/install-ripwire.md for install instructions.

What this measures

Pact coverage answers one question: do the consumer's pact files exercise everything the consumer actually uses from the provider?

The provider's OAS describes its full surface — but the consumer only calls a subset of it. Measuring coverage against the full OAS produces false gaps (unused provider endpoints appearing as uncovered). The correct denominator is the consumer-filtered provider OAS: the slice of the provider's OAS that the consumer actually calls.