Skill
Contract Testing
Adds consumer-driven contract tests between services so a breaking API change fails in CI before it ships to the service that depends on it.
1The consumer writes down what it relies on. The provider proves it still delivers that.
2Steps
31. Identify the pair: one consumer, one provider, one interface (HTTP endpoint or message). Do one pair at a time.
42. Check what the project already uses (Pact, Spring Cloud Contract, schema files). Reuse it. If nothing exists, default to Pact for HTTP and message interactions.
53. Consumer side: record each interaction the consumer code really performs, using its real client. Include the request, the status and only the response fields the consumer reads. Use matchers for types and formats, not literal values.
Claude CodeCodex
Contract Testing
SkillTesting
Free