contract-versioning

What problem does it solve?

Enforces semantic versioning discipline for the shared @template/contracts package so schema shifts never slip through unnoticed and downstream packages avoid unexpected breaking changes.

Core Features & Use Cases

• Semantic Versioning Governance: Determine whether schema edits require patch, minor, or major bumps based on optional versus breaking field changes.
• Change Coordination Workflow: Update the version entry in packages/contracts/package.json, refresh the CHANGELOG.md, and assess impact across consuming packages with the audit checklist.
• Use Case: When a contract field is renamed or removed, trigger a major bump, document the migration guidance, and confirm every consumer is aligned before release.

Quick Start

Run the contract-versioning skill to assess schema changes, bump the packages/contracts version, and update the changelog with impact notes.