contract-review-gate

Compare frontend OpenAPI contracts against backend generated schemas to report drift.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/ringlochid/coding-skills --skill contract-review-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-review-gate
Source: https://github.com/ringlochid/coding-skills/tree/main/contract-review-gate
Command: npx skills add https://github.com/ringlochid/coding-skills --skill contract-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend and backend teams frequently drift from agreed API contracts, causing runtime errors and integration fragility.

Core Features & Use Cases

  • Contract drift detection: Compare frontend OpenAPI/schema/types against backend artifacts to surface mismatches.
  • Impact assessment: Highlight affected endpoints, request/response shapes, and auth/CORS transport inconsistencies.
  • Guided remediation: Recommend minimal, backward-compatible changes to restore alignment.

Quick Start

Run a drift check on the current API contracts and generation artifacts to produce a delta report.

Frequently Asked Questions about contract-review-gate

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

FAQPage Schema
What is API contract drift between frontend and backend?

API contract drift occurs when frontend OpenAPI schemas diverge from backend generated artifacts. This Skill detects mismatches in request/response shapes, auth transport, CORS, enums, and nullability to prevent runtime errors.

How do I detect OpenAPI schema mismatches across web and mobile clients?

You can detect OpenAPI schema mismatches by validating source contracts and generation commands against backend artifacts. This Skill compares frontend types across web and mobile clients to surface drift and produce a delta report.

Can I check for auth session and CORS transport inconsistencies in my API?

Yes, you can check for auth session and CORS transport inconsistencies. This Skill validates API surfaces to highlight affected endpoints and transport layer mismatches between frontend contracts and backend implementations.

What is the best way to fix frontend-backend API drift without breaking changes?

The best way to fix API drift without breaking changes is guided remediation. This Skill recommends minimal, backward-compatible changes to restore alignment between frontend OpenAPI contracts and backend schemas.

Does API contract drift detection work if generation commands are missing?

API contract drift detection requires valid generation commands. This Skill verifies the presence of source contracts and generation commands, flagging missing artifacts as drift proof before completing the validation process.

Why does my frontend OpenAPI schema not match the backend generated schema?

Your frontend OpenAPI schema may not match the backend generated schema due to untracked updates in enums, nullability, or response shapes. This Skill identifies these divergences and flags drift proof with recommended fixes.