contract-compliance-check

Validate ModelTicketContract changes against origin/main and return PASS, WARN, or BLOCK verdicts.

3|1|Updated Oct 9, 2025

Search Tags:#ci/cd #code validation #git diff #api contract #pre-merge check #contract compliance

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill contract-compliance-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contract-compliance-check
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/contract-compliance-check
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill contract-compliance-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents breaking changes from being merged into the main branch by automatically validating code contracts against predefined rules and baseline states.

Core Features & Use Cases

Pre-merge Validation: Ensures that changes to topics, events, protocols, public APIs, and envelopes adhere to contract specifications.
Automated Compliance Checks: Diffs current branch code against origin/main to identify deviations.
Emergency Bypass: Allows for controlled overrides of blocking issues with proper justification and follow-up tickets.
Use Case: A developer is about to merge a feature that modifies an event payload. This skill runs automatically, detects a required field was removed, and blocks the merge, prompting the developer to fix the contract or use the emergency bypass.

Quick Start

Run the contract-compliance-check skill for ticket OMN-1234.

Frequently Asked Questions about contract-compliance-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate API contracts before merging code changes?▼

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.

Can I bypass a pre-merge block if I need to merge an urgent change?▼

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.

How does automated contract compliance checking work for event payloads?▼

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.

What's the best way to prevent breaking changes to public APIs in CI/CD?▼

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.

Why does pre-merge contract validation block my feature branch merge?▼

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.

Do I need a ModelTicketContract to run code validation checks?▼

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.