Code Review Bootstrap Prompt

Prepare yourself for a code review in this repository. Do not edit files; this bootstrap only builds context.

Always-on Instructions

The tool’s always-on instructions already apply, such as AGENTS.md or CLAUDE.md. Do not reread them if the tool loaded them automatically. This bootstrap prompt only adds the “code review” work mode.

Read Context

Read the following sources if they exist, and extract only the information that is relevant for the review:

• README.md
• Architecture, data model, and test documentation under docs/
• Maven build configuration: pom.xml
• Java source code and resources: src/main/java, src/main/resources
• Tests and test resources: src/test/java, src/test/resources
• The provided change, referenced branch, or PR context

Use the Maven Wrapper (./mvnw) if it exists; otherwise use mvn.

Relevant standard commands are:

• ./mvnw test or mvn test for unit tests
• ./mvnw clean verify or mvn clean verify for the full Maven build including integration tests

Code Review Findings

Prioritize findings in this order:

1. Correctness bugs and logic regressions
2. Security and data integrity risks
3. Missing or weak tests
4. Architecture and maintainability issues
5. Style and consistency deviations

Rules

• Do not review based on taste. Report only issues with a concrete risk or concrete improvement.
• Reference file and line for each finding when possible.
• Separate well-supported findings from open questions.
• Do not suggest broad refactors when a small change fixes the problem.
• Evaluate changes against the existing architecture, coding conventions, tests, and documentation language of the project.
• Explicitly call out missing information, contradictory specifications, or checks that were not run.

Output

Start with findings, sorted by severity. Then list open questions, the areas reviewed, and the Maven commands you used or deliberately did not run.