contract-testing SKILL.md skillA
contract-testing from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/contract-testing@git:20261004.4b0ddb9Pins git:20261004.4b0ddb9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/contract-testing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261004.4b0ddb9, committed Oct 4, 2026
- First version recorded
- May 29, 2026
- Size
- 2,193 bytes
- Repository stars
- 74,516
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/contract-testing@sha256:a6f0b49e15f769f0The line at the top of this page pins the label git:20261004.4b0ddb9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_l6bfb2xjz7yhk65x)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Oct 4, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.4b0ddb9 latest | 2026-10-04 | 4b0ddb9 | 2,193 B | A | view · diff |
| git:20260529.7c05904 | 2026-05-29 | 7c05904 | 2,199 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2193 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l6bfb2xjz7yhk65x GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/contract-testing GET https://markdownregistry.com/api/v1/blob/a6f0b49e15f769f0bf7f573c296abd905992fccbf806f9e49d94d26e0876d23a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from thedaviddias/front-end-checklist
Every file in thedaviddias/front-end-checklist