pact-coverage
Runs a coverage check to find which API operations, status codes, request body required fields, and response body required fields are NOT exercised by existing Pact consumer tests. Invoke this skill whenever the user asks "what's not covered by my pacts?", "which endpoints are missing pact tests?", "do my pact files cover the full spec?", "how complete is my pact coverage?", "which required fields aren't tested?", or any time they have Pact v2/v3/v4 JSON files and want to measure contract test coverage against an OpenAPI spec. Also supports AsyncAPI 3.x specs with Pact message pacts (Kafka, SNS/SQS, RabbitMQ events): invoke when the user asks which channels, message variants or required payload fields are not covered by their message pacts. Also invoke when they say they want to improve pact coverage or find coverage gaps — even if they don't say "pact-coverage" explicitly. Do NOT invoke for running provider verification, publishing pacts to a broker, or checking can-i-deploy; use the pactflow skill for those.
Install
With your agent
Install OMGSkills skill "pactflow/pactflow-agent-skills:plugins/swagger-contract-testing/skills/pact-coverage" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/pactflow/pactflow-agent-skills /tmp/pactflow-agent-skills && ln -s /tmp/pactflow-agent-skills/plugins/swagger-contract-testing/skills/pact-coverage ~/.claude/skills/pact-coverageFrom README
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 above), or as a CLI binary for CI scripts (see Scripts (CI / advanced) below). Run command -v ripwire to check; see references/ -ripwire.md for 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.
More from this repo
drift-testing
Verifies API implementations against OpenAPI specifications using the Drift CLI, catching spec drift and supporting...
oas-generator
Generates an OpenAPI 3.x YAML spec from a provider codebase using ripwire when no spec exists.
openapi-parser
Parses complex OpenAPI specs and generates Drift test cases from them.