{"enrichment":{"faq":[{"a":"api-contract-review audits your REST API design against best practices for HTTP verb selection, versioning strategies, and status code correctness. It catches common mistakes like wrong HTTP methods, missing API versions, entity leaks, and improper error handling that break client compatibility.","q":"What does api-contract-review check in my REST API endpoints?"},{"a":"api-contract-review reviews REST API contracts for HTTP semantics and correctness, validating that your endpoints use appropriate HTTP verbs, status codes, and response patterns. It checks controller HTTP verb usage and ensures your API follows REST conventions.","q":"How can I review my REST API endpoints for HTTP semantics?"},{"a":"Yes. api-contract-review audits API versioning and backward compatibility, including versioning in URL paths and deprecation strategy. It identifies breaking changes before releasing API updates and validates your approach to maintaining client compatibility across versions.","q":"Can api-contract-review audit my API versioning strategy?"},{"a":"api-contract-review validates response design, DTOs, and error handling patterns. It checks for entity leaks in REST responses, validates DTO vs entity usage, reviews API status codes and error handling, and audits REST API security in error responses to prevent anti-patterns like 200 OK errors.","q":"What response design issues does api-contract-review validate?"},{"a":"Yes. api-contract-review checks endpoint naming, URL structure, and design consistency. It validates REST endpoint naming conventions and ensures your API follows consistent design patterns across all routes.","q":"Does api-contract-review check endpoint naming conventions?"},{"a":"api-contract-review reviews your API for breaking changes before releasing updates. By auditing versioning strategy, backward compatibility, deprecation practices, and response consistency, it helps you catch compatibility issues that would break existing clients.","q":"How does api-contract-review help identify breaking changes?"}],"shadow_tags":["rest-semantics","api-versioning","http-verbs","backward-compat","dto-patterns","status-codes","error-handling","api-design-audit","endpoint-review","contract-validation"],"summary_rewrite":"Audit your REST API design against best practices for HTTP verb selection, versioning strategies, and status code correctness. Catches common mistakes like wrong HTTP methods, missing API versions, entity leaks, and improper error handling that break client compatibility."},"files":[{"bytes":11060,"path":".claude/skills/api-contract-review/SKILL.md","sha256":"83bf3bc1a3dd0d9d18d95b2e7dc223fe7a67ff8166d2146b46bfbab5411bc8a7","url":"https://skillfed.io/files/decebals/claude-code-java/api-contract-review/7b204709/SKILL.md"}],"id":"decebals/claude-code-java/api-contract-review","links":{"html":"https://skillfed.io/decebals/claude-code-java/api-contract-review","md":"https://skillfed.io/decebals/claude-code-java/api-contract-review.md","repo":"https://github.com/decebals/claude-code-java"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":135,"language":"Shell","last_updated":"2026-02-08","license":"MIT","name":"api-contract-review","publisher":"decebals","stars":693},"relations":{"similar":[{"id":"giuseppe-trisciuoglio/developer-kit/spring-boot-rest-api-standards"},{"id":"decebals/claude-code-java/spring-boot-patterns"},{"id":"personamanagmentlayer/pcl/spring-boot-expert"},{"id":"manutej/luxor-claude-marketplace/spring-boot-development"},{"id":"dawiddutoit/custom-claude/java-spring-service"},{"id":"xu-xiang/everything-claude-code-zh/springboot-patterns"},{"id":"bobmatnyc/claude-mpm-skills/spring-boot"},{"id":"personamanagmentlayer/pcl/java-expert"},{"id":"doccker/cc-use-exp/java-dev"},{"id":"rohitg00/awesome-claude-code-toolkit/springboot-patterns"}]},"slug":{"owner":"decebals","repo":"claude-code-java","skill":"api-contract-review"},"version":"7b204709"}