integration-check

Identify and report FE and BE surface contract mismatches in an Integration Check Report.

Updated Apr 17, 2026

Search Tags:#testing #frontend #integration #backend #compatibility #contract #api-design

Ready to run

npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill integration-check-kingsharkg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integration-check
Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/integration-check
Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill integration-check-kingsharkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compare FE and BE contract surfaces for likely incompatibilities. Use for changed request/response contracts, auth expectations, field names, or nullability.

Core Features & Use Cases

Endpoint-path and method consistency checks across FE/BE contracts
Validation of request/response field names, envelope shapes, and nullability
Verification of authentication expectations, status codes, and error shapes
Generates an Integration Check Report artifact that highlights findings and recommendations

Quick Start

Run a quick compatibility pass between the latest FE and BE contracts to produce an Integration Check Report.

Frequently Asked Questions about integration-check

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

FAQPage Schema

How do I check frontend and backend API contracts for compatibility issues?▼

To check frontend and backend API contracts for compatibility, compare endpoint paths, methods, field names, envelope shapes, and nullability expectations to surface mismatches and generate a structured report of findings.

What is frontend backend contract testing and when do I need it?▼

Frontend backend contract testing validates that API surfaces align when changes occur. You need it to catch mismatches in endpoints, field names, auth requirements, and status-code handling before deployment.

How do I detect API field name and nullability mismatches between client and server?▼

Detect API field name and nullability mismatches by comparing request and response surface contracts directly, validating field names, envelope shapes, and nullability to produce a list of specific compatibility findings.

Can I validate authentication requirements and status code handling across FE and BE contracts?▼

Yes, you can validate authentication requirements and status-code handling by verifying auth expectations and error shapes across frontend and backend contracts to identify incompatibilities in security surface areas.

What is the best way to report API contract deltas after backend changes?▼

The best way to report API contract deltas is to produce a structured Integration Check Report containing metadata, surface deltas, a verdict, detailed findings, and recommended fixes for the identified mismatches.

Does frontend backend contract checking work without external testing dependencies?▼

Yes, frontend backend contract checking works without external testing dependencies, relying solely on comparing the defined contract surfaces to identify incompatibilities and generate the compatibility report.