testing-contract
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-e2eorplaywright). - The scope is isolated unit logic (
testing-unit).
- The scope is visual/UI behavior only (
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
- Define compatibility policy (backward/forward/strict).
- Identify contract surfaces and critical consumers.
- Compare enforcement options and choose one with rationale.
- Capture provider-consumer compatibility in
assets/contract-compatibility-matrix-template.md. - Execute provider and consumer verification runs.
- 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.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9