contract-testing-pact

Verifies providers against consumer Pact contracts and emits a can-i-deploy gate verdict.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill contract-testing-pact-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contract-testing-pact
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/contract-testing-pact
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill contract-testing-pact-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams deploying microservices independently need proof that a provider still satisfies every consumer contract before a release is promoted, and manual verification or self-reported passes cannot be trusted in regulated environments. ## Core Features & Use Cases - Provider Verification: Replays each consumer pact against the provider through the CI/test runner in a sandbox and records per-pact verified results. - can-i-deploy Broker Gate: Queries the Pact Broker to confirm all consumer contracts are verified before promoting a version to an environment. - Runner-Backed Verdicts: Emits a PASS, FAIL, or ERROR verdict with an audit ID, routing failures to a fixer and feeding a human verification layer instead of auto-approving. - Use Case: Before merging a provider change, run the skill with the consumer pacts, provider reference, and target environment to get a gated PASS/FAIL decision backed by real runner and broker evidence. ## Quick Start Verify my provider service against the consumer pacts and check can-i-deploy for the staging environment before I merge this release.

Frequently Asked Questions about contract-testing-pact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Pact contract tests before merging a provider change?▼

Provide the consumer pacts, the provider reference, and the target environment. The skill replays each pact against the provider through the CI/test runner in a sandbox and records a per-pact verified result, never a self-asserted pass.

What is the Pact Broker can-i-deploy check?▼

can-i-deploy is a Pact Broker query that confirms every consumer contract is verified for a given application version before it is promoted to an environment. It is the authoritative pre-deploy gate, so a false result blocks the release even if local verification looks green.

When does the contract test verdict return FAIL versus ERROR?▼

FAIL is returned when any consumer pact is unverified, can-i-deploy is false, or a result is masked or uncertain. ERROR is returned when the verification run or the broker query itself could not execute, which escalates to a human queue.

Can this skill write the API contract or fix failing provider code?▼

No. It only verifies providers against existing consumer pacts. Authoring the API contract belongs to a contract design skill, and failures are routed to a fixer such as progressive-bug-hunter rather than being fixed in place.

What inputs are required to verify a provider against consumer pacts?▼

The input schema requires pacts (the consumer contracts), provider_ref, environment for the can-i-deploy query, and an idempotency key. An optional tier parameter defaults to T2. Missing pacts, provider, or environment stops with a needs-input escalation.