Review a Spring Boot API change end to end
A repeatable sequence for reviewing a Spring Boot API change: scope it, run a structured review, verify with tests, and write the PR description.
Этот ресурс доступен только на английском языке.
Перед началом
- The change is on a branch with a clear description of intent.
- You can run the service's test suite locally.
Шаги
Scope the change
List the endpoints, DTOs and services that changed. Review only these plus their direct collaborators.
Использует: Code review rules for humans and agentsПроверьте, прежде чем продолжить
- You can state in one sentence what the change is supposed to do.
Run a structured review
Paste the changed controller, service and DTO code into the review prompt, choosing the focus that matches the risk.
Использует: Review a Spring Boot REST APIПроверьте, прежде чем продолжить
- Every blocker or major finding has a concrete location and fix.
- Anything under "Needs more context" is resolved or noted.
Cover the gaps with tests
Turn the suggested tests into real ones for the riskiest paths, then run the suite.
Использует: Write JUnit 5 tests for a Java classПроверьте, прежде чем продолжить
- New tests fail without the fix and pass with it.
- The full test command passes locally.
Write the pull request description
Summarize intent, changes, verification steps and risks for the reviewers.
Использует: Write a pull request descriptionПроверьте, прежде чем продолжить
- A reviewer can reproduce your verification steps.
Ожидаемый итог
A reviewed change with test evidence and a pull request description reviewers can act on.
Похожие ресурсы
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Обновлено позавчера
spring-bootrestjavareview
Об этом каталоге
Встроенный снимок · опубликовано 15 нояб. 2026 г., 06:05 · Ревизия каталога 5bc079fe355af2214bc0
Показан снимок, встроенный в приложение (источник контента не настроен). В источнике может быть более свежий контент.