contract-testing

Validate inter-service contracts across REST, gRPC, and async boundaries.

Updated Mar 29, 2026

Search Tags:#openapi #asyncapi #contract-testing #cdc #pact #provider-verification

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill contract-testing-marquesfelip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contract-testing
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/contract-testing
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill contract-testing-marquesfelip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and enforce inter-service contracts to prevent integration regressions across teams and deployments.

Core Features & Use Cases

Identify service boundaries and contract types (HTTP, gRPC, messaging) to map dependencies.
Enable consumer-driven contract (CDC) testing with Pact and provider verification to ensure providers meet consumer expectations.
Integrate with CI/CD and Pact Broker to publish, verify, and gate deployments based on contract health.

Quick Start

Define the consumer and provider contracts for your service boundaries and run the Pact-based provider verification in CI.

Frequently Asked Questions about contract-testing

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

FAQPage Schema

How do I prevent integration regressions between microservices?▼

You can prevent integration regressions by validating inter-service contracts through consumer-driven contract testing, ensuring providers meet consumer expectations across REST, gRPC, and asynchronous event boundaries.

How does consumer-driven contract testing work with Pact?▼

Consumer-driven contract testing with Pact works by having consumers define expected interactions, which providers then verify, ensuring providers meet consumer expectations without requiring full integration tests.

Can I use OpenAPI and AsyncAPI schemas for contract drift detection in CI/CD?▼

Yes, you can use OpenAPI schemas for REST and AsyncAPI schemas for messaging to detect contract drift in CI/CD workflows, validating that service boundaries remain aligned during deployments.

How do I set up provider verification for gRPC and messaging contracts?▼

Provider verification for gRPC and messaging contracts is set up by identifying service boundaries, defining contract types, and running Pact-based verification in CI to ensure providers satisfy consumer expectations.

Do I need a Pact Broker to gate deployments based on contract health?▼

A Pact Broker is optional but recommended to publish, verify, and gate deployments based on contract health, enabling robust consumer-driven contract testing workflows across teams.

When should I not use consumer-driven contracts for API testing?▼

Consumer-driven contracts may not be suitable for simple single-consumer APIs or when rapid prototyping requires frequent breaking changes, as the overhead of maintaining Pact contracts outweighs the integration regression benefits.