api-design-reviewer
FeaturedComprehensive REST API design review with automated linting, breaking-change detection, and design scorecards. Catches inconsistent conventions, missing versioning, and design smells before APIs ship. Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing API standards for a team.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- alirezarezvani
- Repository
- alirezarezvani/claude-skills
- Created
- 10 months ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
api-design-review
Reviews an API surface — REST/OpenAPI, gRPC/proto, GraphQL schema, or CLI — for design quality and evolvability before it is locked. Rates resource modeling, method semantics, versioning, payloads, and security against an opinionated checklist. Use when an API contract is being designed or about to ship and breaking it later is costly.
api-design-reviewer
Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing REST API standards. Triggers on "API review", "REST design review", "breaking change check", "OpenAPI audit", "endpoint review", or "API consistency".
api-design-review
Runs a structured, evidence-based review of API contract design and cross-endpoint consistency across REST, GraphQL, and gRPC surfaces — resource/endpoint naming and HTTP verb correctness, status-code correctness, request/response shape and envelope consistency, error-response format, pagination and filtering conventions, idempotency, versioning strategy, backward compatibility, and documentation/spec-vs-code drift (OpenAPI/Swagger, GraphQL SDL, .proto), plus GraphQL-specific checks (N+1-shaped resolver design, @deprecated usage, query depth/complexity limiting) and gRPC-specific checks (proto field-number stability, proto3 optional/wrappers, service/method naming). This is a design/contract-consistency review, not an authentication/access-control security review (use cybersecurity-check for that) and not a latency/throughput performance review (use performance-audit for that). Use this whenever the user asks for an "API design review", "API review", "API-Design prüfen", "API-Design-Review", "REST API check",