What problem does it solve? REST APIs built with Spring WebFlux often drift from HTTP semantics and internal conventions as they grow — wrong verbs, missing status codes, unhandled domain exceptions falling through to 500, and mixed RouterFunction/@RestController styles. This Skill audits your web layer against a defined rule set and reports every violation with exact file and line locations. ## Core Features & Use Cases - HTTP Semantics Audit: Verifies method usage (POST/GET/PUT/PATCH/DELETE), expected status codes, kebab-case plural URLs, and consistent URL versioning conventions. - Web-Layer Consistency Check: Detects mixed RouterFunction and @RestController usage within the same domain against the configured webLayer setting. - Exception & Pagination Review: Flags domain exceptions without .onErrorResume/@ExceptionHandler mappings and list endpoints missing page size clamps or pagination metadata. - Use Case: Before merging a new EmployeeHandler, run the audit to catch that EmployeeNotFoundException has no error mapping and would surface as a 500 instead of a 404. ## Quick Start Ask the assistant to run be-api-review on a specific handler or controller file, or on the whole codebase, to audit the REST API contracts.