How do I install the Contract Testing skill?

Run npx skillmds@latest add thedaviddias/contract-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Contract Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Contract Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Contract Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Contract Testing?

thedaviddias (@thedaviddias) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Contract Testing by thedaviddias — Agent Skill

Name: Contract Testing
Author: thedaviddias

Contract Testing

Use when setting up integration testing for a frontend-backend API boundary, evaluating whether two services are safe to deploy independently, or replacing slow end-to-end tests with contract tests.

thedaviddias db9bb7f 2 files · 12.1 KB Updated Sep 17, 2026

File contents

Implement consumer-driven contract testing for API boundaries

Integration tests that require both services running at the same time are slow, brittle, and hard to maintain. Consumer-driven contract testing decouples the consumer and provider test suites — each team can run their tests independently, yet the broker guarantees that the published contract is always verified against the live provider. This catches API mismatches days earlier than end-to-end tests, with far less infrastructure overhead.

Quick Reference

The consumer writes tests that describe what it expects from the API (the "contract")
The contract is published to a Pact Broker and verified against the real provider
Provider changes that break the contract fail CI before they are deployed
This replaces fragile end-to-end tests that require both services to be running simultaneously

Check

Check whether the frontend has consumer-driven contract tests that define and verify the API contract with the backend.

Fix

Add Pact consumer tests for the frontend API client, publish the contracts to a broker, and add provider verification to the backend CI pipeline.

Explain

Explain how consumer-driven contract testing works, what the Pact workflow looks like end-to-end, and how it compares to mocking and end-to-end testing.

Code Review

Review the Pact consumer tests. Flag interactions that are too permissive (any-type matchers on fields the consumer actually uses), missing status code assertions, and interactions for endpoints the consumer no longer calls.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/testing/contract-testing

---name: contract-testingdescription: Use when setting up integration testing for a frontend-backend API boundary, evaluating whether two services are safe to deploy independently, or replacing slow end-to-end tests with contract tests.---# Implement consumer-driven contract testing for API boundariesIntegration tests that require both services running at the same time are slow, brittle, and hard to maintain. Consumer-driven contract testing decouples the consumer and provider test suites — each team can run their tests independently, yet the broker guarantees that the published contract is always verified against the live provider. This catches API mismatches days earlier than end-to-end tests, with far less infrastructure overhead.## Quick Reference- The consumer writes tests that describe what it expects from the API (the "contract")- The contract is published to a Pact Broker and verified against the real provider- Provider changes that break the contract fail CI before they are deployed- This replaces fragile end-to-end tests that require both services to be running simultaneously## CheckCheck whether the frontend has consumer-driven contract tests that define and verify the API contract with the backend.## FixAdd Pact consumer tests for the frontend API client, publish the contracts to a broker, and add provider verification to the backend CI pipeline.## ExplainExplain how consumer-driven contract testing works, what the Pact workflow looks like end-to-end, and how it compares to mocking and end-to-end testing.## Code ReviewReview the Pact consumer tests. Flag interactions that are too permissive (any-type matchers on fields the consumer actually uses), missing status code assertions, and interactions for endpoints the consumer no longer calls.---For full implementation details, code examples, and framework-specific guidance,see `references/rule.md`.Rule page: https://frontendchecklist.io/en/rules/testing/contract-testing

Frequently asked questions