contract-compliance-check

To validate API contracts before merging, this Skill reads a ModelTicketContract, diffs the current branch against origin/main, and executes targeted probes on touched interfaces to return a PASS, WARN, or BLOCK verdict.

Yes, you can bypass a pre-merge block by using the emergency bypass mechanism, which downgrades a BLOCK to a WARN when you provide justification and a follow-up ticket for the contract deviation.

Automated contract compliance checking works by diffing your current branch against origin/main to identify deviations in event payloads, topics, and public APIs, ensuring modified required fields adhere to baseline specifications.

The best way to prevent breaking changes to public APIs in CI/CD is to run pre-merge seam validation that automatically detects removed required fields and blocks the merge before code reaches the main branch.

Pre-merge contract validation blocks your feature branch merge because it detected a contract specification violation, such as a removed required field from an event payload or public API envelope during the branch diff.

Yes, you need a ModelTicketContract to run code validation checks, as the Skill reads this contract to understand the predefined rules and baseline states required to execute targeted probes on touched interfaces.