Skill

contract-testing

Sets up Pact contract testing for microservices: consumer-driven contracts with provider states and interactions, verification via state handlers, OpenAPI validation middleware, breaking change detection.

Express

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

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/billy-milligan:contract-testing

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlob

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Building microservices that need integration confidence

Supporting Files

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

SKILL.md

31 lines · ~371 tokens

Similar Skills

validating-api-contracts

2.2k

Validates API contracts with Pact (JS/Python/JVM) and Spring Cloud Contract via consumer-driven testing. Prevents microservice breaking changes.

8 files6 tools

contract-test-validator

api-contract-testing

149

Verifies API contracts between services using Pact consumer-driven tests, provider verification, schema validation, and OpenAPI specs. Use for microservices communication, preventing breaking changes.

3 files

api-contract-testing

Test Contract Testing

Verifies service compatibility using Pact consumer-provider contract tests. Useful for preventing breaking changes across independently deployed services.

1 file

harness-claude

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceExcellent

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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