contract-sync-audit

Audits backend routes against frontend API calls and emits a reconciliation report.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/FerEscobarDev/Specture --skill contract-sync-audit-ferescobardev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contract-sync-audit
Source: https://github.com/FerEscobarDev/Specture/tree/main/skills/contract-sync-audit
Command: npx skills add https://github.com/FerEscobarDev/Specture --skill contract-sync-audit-ferescobardev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend and backend codebases drift apart over time: the frontend calls URLs the backend never exposes, expects response shapes the backend doesn't return, or uses different HTTP methods and paths. This Skill statically extracts both sides, diffs them against a canonical source of truth, and produces a reconciliation report — without auto-fixing anything. ## Core Features & Use Cases - Deterministic route extraction: Parses backend routes from OpenAPI/Swagger endpoints or framework-specific decorators (Express, NestJS, FastAPI, Spring, ASP.NET, Rails, Laravel) and frontend calls from fetch, axios, HttpClient, React Query, or SWR. - Classified diff report: Categorizes findings as missing endpoints, URL/method/shape mismatches, orphan endpoints, auth mismatches, or unresolved dynamic paths, each cited with file:line pinned to the audited commit SHA. - Canonical contract generation: When no API contract exists, proposes an OpenAPI contract file as the new single source of truth, then routes fixes to build/new-feature/debug workflows. - Use Case: Before importing a design handoff into a project whose API has drifted, run the audit to wire the new UI against a coherent, verified contract. ## Quick Start Audit my project's backend routes and frontend API calls for mismatches and generate a contract sync report.

Frequently Asked Questions about contract-sync-audit

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

FAQPage Schema
How do I find mismatches between my frontend and backend API?▼

Run a contract sync audit that statically extracts backend route definitions and frontend API calls, then diffs them. Findings are classified as missing endpoints, URL or method mismatches, shape mismatches, orphan endpoints, or auth mismatches, each cited with file and line on both sides.

How to detect frontend calls to backend endpoints that don't exist?▼

The audit extracts every fetch, axios, HttpClient, or React Query call in the frontend and compares each method and path against routes parsed from the backend. Calls with no matching backend route are reported as missing endpoints that would 404 in production.

Which backend frameworks are supported for route extraction?▼

Route extraction supports Express, Fastify, NestJS, Spring, FastAPI, Flask, ASP.NET, Go frameworks like gin and echo, Rails, and Laravel. The most reliable input is a served OpenAPI or Swagger schema, which is parsed directly when available.

Does the contract sync audit automatically fix API mismatches?▼

No, the audit never modifies application code. It produces a reconciliation report with proposed changes stated against a canonical source, then routes each fix to build, new-feature, or debug workflows that require their own specs.

What are the limitations of static API contract analysis?▼

Dynamically typed backends expose no response types, so shape mismatches there are heuristic and marked unresolved. URLs built at runtime from variables cannot be fully resolved statically and are flagged rather than guessed.