From backend-springboot-plugin
Audit REST API contracts for HTTP semantics, versioning, and consistency.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-springboot-plugin:be-api-reviewThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Audit REST controllers for HTTP semantics, URL patterns, status codes, and consistency.
Audit REST controllers for HTTP semantics, URL patterns, status codes, and consistency.
.claude/backend-springboot-plugin.json/backend-springboot-plugin:be-init first and stop@RestController classes in {sourceDir}/{basePackage}/Check each controller against these rules:
| Method | Expected Use | Expected Status |
|---|---|---|
@PostMapping | Create new resource | 201 Created |
@GetMapping | Read resource(s) | 200 OK |
@PutMapping | Full resource replace | 200 OK |
@PatchMapping | Partial update | 200 OK |
@DeleteMapping | Remove resource | 204 No Content |
Flag violations:
@ResponseStatus when status differs from 200/hr/employees, not /hr/Employees or /hr/employee_list/employees, not /employee/{domain}/{resources}/{id}/{sub-resources}/employees/createcommand/ package)view/ package)@PathVariable UUID id@RequestParam@ExceptionHandler methods for domain exceptions@ControllerAdvicepage and size parametersrecord class (for CQRS architecture)Display findings in the working language:
API Contract Audit
==================
Controllers reviewed: {count}
Endpoints reviewed: {count}
Issues:
{severity} | {controller}:{method} | {rule} — {description}
Suggestion: {fix}
Endpoint Summary:
{method} {url} → {status} {response type}
npx claudepluginhub ohmyhotelco/hare-cc-plugins --plugin backend-springboot-pluginReviews Java Spring Boot REST API controllers for HTTP methods, status codes, URL naming, DTOs, error formats, versioning, and security basics. Ideal for 'review my API' requests.
Provides REST API standards for Spring Boot covering URL design, HTTP methods, DTOs, validation, error handling, pagination, and security headers. Use when creating or reviewing endpoints.
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".