Agent skill · Testing & QA

contract-test-framework

Consumer-driven contract testing for SDK-API compatibility. Generate Pact consumer tests, verify provider contracts, configure Pact broker, and implement can-i-deploy checks.

a5c-aigithub.com/a5c-aiGitHub ↗
claude-codecodexcan modify filesMIT
Install
npx skills add a5c-ai/babysitter --skill contract-test-framework --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 18 KB
Bundled scripts: none
Version: 1.0.0
Declared author: babysitter-sdk
Allowed tools: Bash(*)ReadWriteEditGlobGrepWebFetch
Path: library/specializations/sdk-platform-development/skills/contract-test-framework/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,642
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# contract-test-framework You are **contract-test-framework** - a specialized skill for consumer-driven contract testing between SDKs and APIs, ensuring compatibility and preventing breaking changes through automated verification. ## Overview This skill enables AI-powered contract testing including: - Generating Pact consumer contracts from SDK usage - Configuring Pact Broker for contract management - Provider verification against consumer contracts - Can-i-deploy safety checks before releases - Breaking change detection and alerting - Webhook integration for automated verification - Support for bidirectional contract testing ## Prerequisites - Node.js 18+ or Python 3.8+ - Pact library for your SDK language - Pact Broker (PactFlow recommended) or self-hosted - CI/CD pipeline access - Consumer SDK and provider API access ## Capabilities ### 1. Consumer Contract Generation for SDKs Generate contracts from SDK tests: ```typescript // tests/contracts/user-api.pact.ts import { PactV3, MatchersV3 } from '@pact-foundation/pact'; import { MyServiceSDK } from '@company/myservice-sdk'; const { like, eachLike, regex, uuid, datetime, integer } = MatchersV3; const provider = new PactV3({ consum

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Capabilities
  4. 1. Consumer Contract Generation for SDKs
  5. 2. Multi-SDK Contract Testing
  6. 3. Provider Verification
  7. 4. CI/CD Pipeline Integration
  8. 5. Webhook Configuration
  9. 6. Breaking Change Detection
  10. MCP Server Integration
  11. Best Practices
  12. Process Integration
  13. Output Format
  14. Error Handling
Ships with 1 file
  • README.md
Commands it runs
Create webhook for SDK changes
pact-broker create-webhook \
Create webhook for verification results
More from babysitter
All skills →
generating-gcp-diagramsGenerates DrawIO XML diagrams for Google Cloud Platform architectures from text descriptions or…DevOps & Cloudgenerating-aws-diagramsGenerates DrawIO XML diagrams for Amazon Web Services architectures from text descriptions or…DevOps & Cloudcorrosion-materials-selectorMaterials selection skill for corrosion resistance based on process conditions and industry…AI & Agentsapi-diff-analyzerCompare API specifications to detect breaking changes. Compare OpenAPI spec versions, categorize…Databasesdistillation-designerDistillation column design skill for tray/packing selection, hydraulic analysis, and column…Design & Presentationcrystallizer-designerCrystallization process design skill for nucleation control, crystal size distribution, and…Design & Presentation
About this skill
What does the contract-test-framework skill do?

Consumer-driven contract testing for SDK-API compatibility. Generate Pact consumer tests, verify provider contracts, configure Pact broker, and implement can-i-deploy checks.

How do I install it?

Run `npx skills add a5c-ai/babysitter --skill contract-test-framework --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.