/contract-test

Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces.

BOOST

archive228@archive228

GitHub

From plugin

loopkit

75553 skills1 agent4 commands2 MCP

Install

$ npx -y skills add Archive228/loopkit --skill contract-test --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/contract-test

Context preview

The summary Claude sees to decide when to auto-load this skill.

Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces.

SKILL.md

contract-test.SKILL.md

name: contract-test
description: Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces.
when_to_use: an API endpoint, a service integration, a webhook, a shared schema

Contract Test

Test what the two sides AGREED on, so either can change internals without breaking the other.

Assert the **shape**: required fields, types, status codes, error format — not internal logic.
Cover the contract's edges: missing optional fields, the documented error responses, pagination bounds, versioning.
For consumers: test against the real contract (recorded/real responses), not a mock you wrote to match your assumptions — that mock drifts and lies.
One source of truth for the schema; both sides validate against it.

A green unit test with a wrong mock is worse than no test. Pin the contract.

Read it on GitHub ↗

Ships withloopkit

33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI).

Get the whole plugin

Stats

Node Bash SQL Git GitHub

+4 tags

Markdown Anthropic Gemini MCP

755

Stars

124