api-check
/api-check
Compare frontend API requests and consumers with backend routes to find mismatches in methods, paths, field names, response shapes, and error handling. Use for API integration reviews and debugging frontend/backend contract incompatibilities; report exact mismatches with file references.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Compare frontend API requests and consumers with backend routes to find mismatches in methods, paths, field names, response shapes, and error handling. Use for API integration reviews and debugging frontend/backend contract incompatibilities; report exact mismatches with file references.
Original author description
Compare frontend API requests and consumers with backend routes to find mismatches in methods, paths, field names, response shapes, and error handling. Use for API integration reviews and debugging frontend/backend contract incompatibilities; report exact mismatches with file references.
How it works
- When to Use
- Instructions
- Examples
SKILL.md preview
--- name: api-check description: Compare frontend API requests and consumers with backend routes to find mismatches in methods, paths, field names, response shapes, and error handling. Use for API integration reviews and debugging frontend/backend contract incompatibilities; report exact mismatches with file references. metadata: categories: Debugging, Frontend, Backend maintainers: ItayShar --- # API Check ## When to Use Use this skill to review API integrations or diagnose incompatibilities between frontend requests and backend routes. ## Instructions Audit frontend/backend contracts within the requested feature, endpoints, or diff. If no scope is specified, inventory callers and routes in the available project. Report findings; edit code only if fixes are requested. ### Compare effective behavior Trace frontend calls through shared clients, serializers, interceptors, base URLs, and proxies to mounted backend routes, validators, handlers, and response middleware. Trace returned data through client transforms to actual consumers. Account for route prefixes and rewrites before declaring a route missing. Use runtime implementation as evidence, checking schemas, generated clients, types, and tests for drift. Compare: - Methods and paths: HTTP verbs, effective URLs, route parameters, query parameters, encoding, and relevant routing behavior. - Request fields: exact names and nesting, body/query/path placement, content type, required fields, nullability, types, enums, and defaults. Account for aliases, serialization, and coercion actually applied. - Response shapes: status codes, empty bodies including 204, envelopes, arrays versus objects, field names, nesting, pagination, nullability, and serialized values. Compare what consumers read against each relevant server response branch. - Error handling: validation, authentication/authorization, not-found, and application errors. Follow status codes and error payloads through middleware and client wrappers to catch branches or UI handling. Check rejection of non-success statuses, error field access, and parsing of empty or non-JSON bodies. Distinguish network failures from server responses. Different variable names, unused response fields, unused backend routes, or types reconciled by adapters are not evidence of a mismatch. Use existing tests or isolated local checks when needed; do not call live mutating endpoints merely to verify contracts. ### Report findings Lead with confirmed mismatches ordered by user impact. For each, provide: - The affected operation and exact frontend request or expectation versus backend requirement or output. Use concrete field paths and values where useful. - Verified file and line references for both sides, plus relevant wrapper or configuration evidence. For missing routes, cite the caller and searched registration locations and scope rather than inventing a definition. - The trigger, observable consequence, and minimal alignment recommendation. If the intended contract is unclear, explain the choice without assuming which side must change. Consolidate symptoms sharing a root cause. Separate unverified concerns from confirmed findings and identify missing evidence. Finish with inspected coverage, validation performed, and limitations such as missing repositories or dynamic routes. If no mismatches are found, say so only within the inspected scope. ## Examples - "Use $api-check to compare the checkout frontend requests with backend routes. Report exact mismatches with file and line references." - "Review this diff for API contract drift, including request fields, response shapes, and error handling." Example finding (illustrative file references): `frontend/orders.ts:42` sends `customerId`, but `backend/orders.ts:18` requires `customer_id`. Submitting an order fails validation with HTTP 400. Align the submitted field name with the accepted contract.
Versions
The database has no other skills named api-check.
Database snapshot: 13.11.2026 · package version 0727e703d705 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100debug-fe-be-integration
Diagnose and fix frontend↔backend contract failures by tracing requests, server logs, validation, auth, and responses on both sides. Use for API 4xx/5xx, mismatched payloads, or "frontend and backend disagree". One layer → debug-error. - 100backend-to-frontend-handoff-docs
Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'. - 100audit-fe-api
Audit frontend API calls against backend implementation for contract alignment and network shape. Use when "API audit", "FE-BE contract", or "review frontend API integration". Live 4xx/5xx reproduction → debug-fe-be-integration. - 100frontend-to-backend-requirements
Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI. - 100api-doc-review
Use when API documentation may have drifted from the implementation -- endpoints changed without a spec update, integration partners report mismatches, or a PR touches routes, params, or response shapes. - 100api-contract
Configure this skill should be used when the user asks about "API contract", "api-contract.md", "shared interface", "TypeScript interfaces", "request response schemas", "endpoint design", or needs guidance on designing contracts that coordinate backend and frontend agents. Use…