- Write review comments in Korean using concise, clear, and easy-to-scan wording.
- This repository is a Spring study repository, not a production service.
- Prioritize feedback that improves Spring understanding over feedback aimed at production hardening.
- Focus on recurring learning issues such as layering, naming, dependency injection, object responsibilities, JPA basics, N+1 risks, circular references, entity/DTO separation, exception handling, and test intent.
- Review comments should explain: 1) what is problematic, 2) why it matters in Spring/Java terms, 3) how to improve it, and 4) which concept to study next.
- Treat preference-based style comments as suggestions, not must-fix issues.
- Review from a study perspective, not a product delivery perspective.
- Use the closest workspace-level AGENTS.md to adjust review depth for junior vs senior members.