api-review

Review API designs for REST consistency and endpoint quality issues.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/rauly-1408/order-saas --skill api-review-rauly-1408
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-review
Source: https://github.com/rauly-1408/order-saas/tree/main/.claude/skills/api-review
Command: npx skills add https://github.com/rauly-1408/order-saas --skill api-review-rauly-1408

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers identify REST API design issues, inconsistent endpoint behavior, and missing production safeguards before APIs are released or scaled.

Core Features & Use Cases

  • REST API Auditing: Reviews endpoint naming, HTTP methods, status codes, pagination, filtering, versioning, and response formats against established API practices.
  • Consistency Analysis: Detects mismatched conventions, weak error handling, missing idempotency protections, and other maintainability risks across API surfaces.
  • Use Case: A backend team preparing a public API release can use this Skill to generate a detailed review report with actionable fixes for every discovered issue.

Quick Start

Use the api-review skill to audit the entire API surface in this codebase and produce a REST best practices report.

Frequently Asked Questions about api-review

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

FAQPage Schema
How do I audit my REST API design for consistency issues before a release?

To audit REST API consistency, review endpoint naming, HTTP methods, status codes, pagination, and response formats against established practices to identify design flaws and improve endpoint quality before release.

What is semantic HTTP validation and how does it improve backend interfaces?

Semantic HTTP validation checks endpoint behavior against standard HTTP methods and status codes to ensure REST consistency, detecting mismatched conventions and weak error handling across backend API surfaces.

How do I check my API endpoints for missing idempotency protections?

Checking API endpoints for missing idempotency protections involves performing a consistency analysis across your API surface to detect maintainability risks and generate actionable findings for fixes.

Can I use an endpoint audit to prepare a public API for production scale?

Yes, an endpoint audit evaluates HTTP interfaces and response formats across common web frameworks to find missing production safeguards, preparing your public API for stable release and scaling.

What is the best way to generate an actionable report for REST API issues?

The best way to generate an actionable REST API report is to discover endpoints, validate semantic HTTP behavior, analyze response formats, and compile the discovered issues into a detailed review report.

Why does my API review report show inconsistent endpoint naming conventions?

An API review report shows inconsistent endpoint naming because the audit process detects mismatched conventions and weak error handling across the API surface, highlighting maintainability risks in your codebase.