Skill

contract-testing

Contract testing: Pact consumer-driven contracts (provider states, interaction definitions), provider verification with state handlers, OpenAPI validation middleware, breaking change detection. Use when microservices need integration confidence without full e2e tests.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Building microservices that need integration confidence

Supporting Assets

references/api-compatibility.mdreferences/pact-patterns.mdreferences/schema-validation.md

SKILL.md

Similar Skills

crosspost

Adapts content for unique crossposting to X, LinkedIn, Threads, and Bluesky using platform constraints and voice preservation. For multi-platform launches, essays, or announcements.

everything-claude-code

156.2k

ai-first-engineering

Provides process, architecture, review, hiring, and testing guidelines for engineering teams relying on AI code generation.

everything-claude-code

156.2k

cpp-testing

Assists writing, fixing, configuring C++ tests with GoogleTest/GoogleMock and CMake/CTest. Diagnoses flaky tests, failures, and adds coverage/sanitizers.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

Core principles

Consumer drives the contract — the client defines what it actually needs

Provider verifies against consumer contracts — not against a human-written spec

Contracts live in Pact Broker — visible to all teams, tracked over time

State handlers make tests reproducible — provider sets up data for each interaction

Can-I-Deploy check — never deploy a provider that breaks a consumer contract

References available

references/consumer-pact-test.md — PactV3 setup, MatchersV3, interaction definition, executeTest

references/provider-verification.md — Verifier config, stateHandlers, Pact Broker publish, CI flags

references/openapi-validation.md — express-openapi-validator middleware, validateResponses in staging

references/can-i-deploy.md — pact-broker CLI check, CI gate before deploy, exit code semantics

Contract Testing

When to use

Building microservices that need integration confidence
Replacing brittle integration tests with faster contract tests
Detecting breaking API changes before deployment
Setting up provider verification in CI

Core principles

Consumer drives the contract — the client defines what it actually needs
Provider verifies against consumer contracts — not against a human-written spec
Contracts live in Pact Broker — visible to all teams, tracked over time
State handlers make tests reproducible — provider sets up data for each interaction
Can-I-Deploy check — never deploy a provider that breaks a consumer contract

References available

references/consumer-pact-test.md — PactV3 setup, MatchersV3, interaction definition, executeTest
references/provider-verification.md — Verifier config, stateHandlers, Pact Broker publish, CI flags
references/openapi-validation.md — express-openapi-validator middleware, validateResponses in staging
references/can-i-deploy.md — pact-broker CLI check, CI gate before deploy, exit code semantics