agentsclimarketplace
Sign in

Testing contract

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-contract

Provider-consumer compatibility testing for service interface changes. Use when APIs or event schemas evolve and executable contract checks must guard compatibility before release; do not use for UI-only validation or architecture topology decisions.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill testing-contract

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 369 tokens by cl100k_base, as published. Nobody here has run it

Testing Contract

Overview

Use this skill to prevent integration regressions by enforcing provider-consumer contracts in CI.

Scope Boundaries

  • Use when interface compatibility between producer and consumer is a release risk.
  • Typical requests:
    • Verify an API response change does not break existing consumers.
    • Enforce event schema compatibility in CI.
    • Add provider-consumer contract gates before merge.
  • Do not use when:
    • The scope is visual/UI behavior only (testing-e2e or playwright).
    • The scope is isolated unit logic (testing-unit).

Inputs

  • Contract definitions and compatibility policy
  • Provider/consumer versioning constraints
  • Release and rollback requirements

Outputs

  • Versioned contract suite and compatibility matrix
  • Decision record for contract strategy and migration path
  • Verification checklist for provider and consumer pipelines

Workflow

  1. Define compatibility policy (backward/forward/strict).
  2. Identify contract surfaces and critical consumers.
  3. Compare enforcement options and choose one with rationale.
  4. Capture provider-consumer compatibility in assets/contract-compatibility-matrix-template.md.
  5. Execute provider and consumer verification runs.
  6. Publish failures, migration actions, and residual risk.

Quality Gates

  • Compatibility policy is explicit and test-enforced.
  • Breaking changes include migration and communication plan.
  • Contract evidence is reproducible in CI.
  • Residual compatibility risk is owned and tracked.

Failure Handling

  • Stop when required compatibility policy is violated.
  • Escalate when no feasible migration path exists.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.
  • assets/contract-compatibility-matrix-template.md: compatibility and migration tracking matrix.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.