agentleFS
saitarrunsaitarrun/Devforge-ai/skills/contract-testing/SKILL.md

contract-testing

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Consumer-driven contract testing, OpenAPI spec drift validation, and breaking API change detection for microservices.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use release-notes and security-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    release-notes

    Author and update release notes for Azure App Configuration libraries and providers. USE FOR: write release notes, add release note entry, update release notes, draft release notes, new version release notes, format release notes. DO NOT USE FOR: generating changelogs from git history, writing internal engineering notes.

    Also in 3 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Breaking Change Detection: Run oasdiff or openapi-diff in CI/CD to block backward-incompatible changes (e.g.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Contract Testing & OpenAPI Validation Skill

This skill ensures microservices communicate reliably via explicit, version-controlled contracts without breaking downstream consumers.

Core Architectural Pillars

1. OpenAPI & Schema Drift Validation

  • Spec-First & Code-First Sync: Enforce strict TypeScript/Zod/JSON Schema generation from OpenAPI 3.1 definitions.
  • Breaking Change Detection: Run oasdiff or openapi-diff in CI/CD to block backward-incompatible changes (e.g. removed fields, altered types, tightened validation).

2. Consumer-Driven Contract Testing (Pact)

  • Consumer Contracts: Downstream microservices define expected API requests and responses.
  • Provider Verification: Upstream microservice verifies actual endpoint execution against consumer expectations before deployment.
  • Pact Broker Matrix: Track deployment status across environments to prevent deploying incompatible service versions.

3. Mock Service Worker (MSW) & Integration Mocks

  • Deterministic API Fixtures: Shared MSW handlers across unit, component, and E2E tests.
  • Network Level Interception: Mock API traffic at network level to avoid fragile global fetch overrides.

Checklist for Slices with needs_contract_testing: true

  • OpenAPI 3.1 schema defined or updated
  • Breaking change check passes against main branch schema
  • Consumer Pact tests generated or MSW handlers synchronized
  • Provider endpoint verification passes end-to-end

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.