api-contract-review

Review REST API contracts for semantic HTTP issues and compatibility risks.

Updated May 15, 2026

Search Tags:#api #openapi #backend #rest #contract review #http semantics

Ready to run

npx skills add https://github.com/avgarcia/runcriticon --skill api-contract-review-avgarcia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-contract-review
Source: https://github.com/avgarcia/runcriticon/tree/main/.claude/skills/api-contract-review
Command: npx skills add https://github.com/avgarcia/runcriticon --skill api-contract-review-avgarcia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch API contract issues before release by reviewing REST endpoints, HTTP semantics, compatibility risks, and consistency with project architecture rules.

Core Features & Use Cases

REST Contract Auditing: Reviews controllers and OpenAPI specifications for endpoint correctness, DTO usage, HTTP behavior, and versioning decisions.
Compatibility Validation: Detects breaking API changes, missing authorization rules, response inconsistencies, and violations of established project conventions.
Use Case: Before merging a pull request that changes API endpoints, use this Skill to identify contract problems and generate a structured review report.

Quick Start

Ask the api-contract-review skill to review the changed REST endpoints and OpenAPI specification for compatibility issues.

Frequently Asked Questions about api-contract-review

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

FAQPage Schema

How do I review REST API contracts for breaking changes before a release?▼

Review REST API contracts by validating endpoint correctness, HTTP semantics, DTO boundaries, and versioning decisions to detect breaking changes and compatibility risks before release.

What does semantic HTTP validation check for in OpenAPI specifications?▼

Semantic HTTP validation checks OpenAPI specifications for incorrect endpoint behavior, inconsistent error response mappings, missing authorization annotations, and DTO boundary violations.

How do I catch missing authorization rules in controller changes during a pull request review?▼

Catch missing authorization rules during pull request reviews by auditing controller changes against project-specific API conventions, validating authorization annotations, and mapping error responses.

Can I use this to validate API versioning rules and DTO boundaries in my backend?▼

Yes, you can validate API versioning rules and DTO boundaries in backend controllers by reviewing REST endpoints against established project architecture conventions and HTTP semantics.

What is the best way to ensure consistent error response mappings across REST endpoints?▼

Ensure consistent error response mappings across REST endpoints by auditing OpenAPI updates and controllers to identify inconsistencies, validate HTTP semantics, and generate structured review reports.