Spring Boot: Perch rule pack
2 saved requirements for Spring Boot. Inspect the selectors and adapt the example paths to your repository.
- name: confirmation-transaction-boundary
where: "src/main/java/example/ConfirmOrder.java"
each: method
ensure: >-
The confirm method is explicitly annotated @Transactional. A confirm method without that annotation does not satisfy this required service transaction boundary.
- name: method-security-write-authority
where: "src/main/java/example/CancelOrder.java"
ensure: >-
The public cancel service method must require orders:write with @PreAuthorize before invoking the mutation repository.
Download the rule pack ZIP · Download YAML · Agent repair task · Implementation, integration requirements and captured checks
Install the rule without replacing your configuration
npm install -g @lakeday/perch
perch login
curl -fL 'https://reporules.fyi/spring-boot/rule-pack.zip' -o 'perch-guide-spring-boot.zip'
unzip -n 'perch-guide-spring-boot.zip'Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-spring-boot.yaml. Review each where selector before running a check on your application.
Configure your coding agent
perch setup claude-code
perch setup codex
perch setup cursor
perch setup piChoose the setup command for the agent you use.
Check the edit, fix the finding, check again
perch check src/main/java/example/ConfirmOrder.java::confirm --rules confirmation-transaction-boundary --json
perch check src/main/java/example/CancelOrder.java --rules method-security-write-authority --jsonRun the check after an agent edit. Read the finding and affected code, repair the implementation, and repeat the identical command. Keep the application regression tests as separate gates.
Exit 3 means a finding. Exit 1 or 2 means the check did not complete. A pass does not prove application correctness. Fresh judgments can vary; unchanged requests reuse cached answers. Relevant source is sent to the configured model service.