Review a Spring Boot REST API
A structured review prompt for Spring Boot controllers and services that checks API design, validation, error handling, security and performance, and returns findings ranked by severity.
Этот ресурс доступен только на английском языке.
Промпты — это текст, который вы копируете в своего помощника. KitLocal их не запускает.
Заполните переменные
Include the request/response DTOs so validation can be assessed.
Всё, что вы вводите, остаётся в этом браузере. Это не добавляется в URL, не сохраняется и никуда не отправляется.
Предпросмотр
Ещё нужно: Code under review
You are a senior Java engineer reviewing a Spring Boot REST API change.
Spring Boot version: 3.x
Review focus: All areas
Team conventions (treat as requirements, do not argue with them):
Review the code below. For every finding give: severity (blocker / major / minor / nit),
the exact location, why it matters, and a concrete fix (code when it is short).
Check, as far as the focus allows:
- HTTP semantics: status codes, idempotency, resource naming, pagination, versioning.
- Input validation: Bean Validation annotations, trusting client IDs, mass assignment.
- Error handling: consistent error body, no stack traces or internals leaking.
- Security: authentication/authorization on each endpoint, injection, sensitive data in logs.
- Data access: N+1 queries, missing transactions, unbounded result sets.
- Testability: logic that is hard to unit test, missing test cases worth adding.
Do not invent code that was not provided. If something cannot be judged from the snippet,
list it under "Needs more context" instead of guessing.
Code:
```java
{{code}}
```
Назначение
Get a senior-reviewer style pass over a Spring Boot endpoint before you open a pull request.
Когда использовать
- You changed or added a controller, service or DTO and want a second pair of eyes.
- You inherit an API and need a quick risk map before touching it.
Что подготовить
- The controller, service and DTO code under review (not the whole repository).
- The Spring Boot version and any team conventions that differ from the defaults.
Ожидаемый результат
Markdown: a short summary, then findings grouped by severity (each with location, reason, fix), then a 'Needs more context' list and 3 suggested tests.
Об этом каталоге
Встроенный снимок · опубликовано 15 нояб. 2026 г., 06:05 · Ревизия каталога 5bc079fe355af2214bc0
Показан снимок, встроенный в приложение (источник контента не настроен). В источнике может быть более свежий контент.