skills.rest
peppone-choi
peppone-choiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-api-parity

Validate frontend API client methods against backend controller endpoints.

Updated May 29, 2026
Search Tags:#code quality#full-stack#frontend#api#validation#backend#parity
One-click install
npx skills add https://github.com/peppone-choi/opensamguk --skill verify-api-parity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-api-parity
Source: https://github.com/peppone-choi/opensamguk/tree/main/.claude/skills/verify-api-parity
Command: npx skills add https://github.com/peppone-choi/opensamguk --skill verify-api-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your frontend API calls perfectly match your backend endpoints, preventing integration errors and identifying unused code.

Core Features & Use Cases

  • Full-Stack API Matching: Verifies 1:1 parity between frontend API client methods and backend controller endpoints.
  • Code Health: Detects orphaned service/repository methods and dead API endpoints.
  • Use Case: After implementing a new feature, run this Skill to confirm that every button click on the frontend correctly triggers the intended backend API call, and that no backend code is left unused.

Quick Start

Run the verify-api-parity skill to check for inconsistencies between frontend API calls and backend endpoints.

Frequently Asked Questions about verify-api-parity

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

FAQPage Schema
How do I check frontend and backend API consistency across my full stack?▼

Validating full-stack API consistency involves cataloging backend controller endpoints and frontend API client methods, then cross-validating them to ensure precise 1:1 method-level matching and prevent integration errors.

How can I find dead API endpoints and orphaned service methods in my codebase?▼

You can find dead API endpoints and orphaned repository methods by cross-validating frontend API calls against backend controllers, which identifies unused backend endpoints and disconnected service or repository methods.

What is method-level API parity validation?▼

Method-level API parity validation is the process of ensuring frontend API client methods precisely match backend controller endpoints, confirming request and response type compatibility across the full stack.

When do I need to validate API request and response type compatibility?▼

You need to validate API request and response type compatibility after implementing a new feature to confirm that frontend actions correctly trigger intended backend API calls without type mismatches or orphaned code.

Does this API validation approach require specific frameworks to check controller endpoints?▼

Checking controller endpoints and frontend API client methods requires no specific framework dependencies, as the validation operates by cataloging endpoints and calls, then performing cross-validation and code analysis.

Related Skills

Explore More Software Engineering Skills→
aslaiiaslaii

fullstack-bridge

Synchronize NestJS DTOs with TypeScript interfaces and generate TanStack hooks.

Community
Intermediate
carlos18bpcarlos18bp
1

repo-cleanup

Audit repositories for obsolete files and recommend .gitignore patches.

Community
Advanced
LongTermSupportLongTermSupport

phpstan-runner

Executes PHPStan static analysis and iteratively applies fixes until clean.

Official
Intermediate
ivanyeorsivanyeors

integration

Validate frontend-backend API contracts against OpenAPI specifications.

Community
Advanced