code-review

Reviews Java Spring Boot code changes using prioritized checklists for security, architecture, quality, and testing.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/balajirags/aifsd-kit --skill code-review-balajirags
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/balajirags/aifsd-kit/tree/main/docs/skills/code-review
Command: npx skills add https://github.com/balajirags/aifsd-kit --skill code-review-balajirags

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews on Java Spring Boot projects are often inconsistent, with reviewers missing security flaws or architectural violations while nitpicking style. This Skill provides a structured, priority-ordered review process so critical issues are caught first and feedback is actionable. ## Core Features & Use Cases - Prioritized Review Checklists: Four tiers covering security (input validation, SQL injection, OAuth2/JWT), DDD/CQRS architectural compliance, SOLID/clean code principles, and testing with JUnit 5, Mockito, and TestContainers. - Standardized Output Format: Produces a review summary with severity ratings, critical issues with file:line references, suggestions, and positive observations. - Anti-Pattern Detection: Flags common violations such as domain logic in validators, N+1 queries, magic numbers, and methods over 30 lines. - Use Case: A reviewer receives a pull request touching Spring Boot controllers and JPA entities; the Skill walks them through security checks first, then architecture and quality, producing a structured review comment ready to post. ## Quick Start Review the changed files in this pull request using the code review checklist and produce a prioritized findings summary.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Java Spring Boot code systematically?

Follow a priority-ordered checklist: start with security issues like input validation and SQL injection, then check DDD/CQRS architectural compliance, then code quality principles like SOLID and DRY, and finally test coverage with JUnit 5 and Mockito.

What security issues should I check in a Spring Boot code review?

Check that user inputs are validated and sanitized, JPA queries use parameterized statements, OAuth2 JWT validation and scope checks are correct, and no secrets or PII appear in logs or responses. Required headers should also be validated.

How should code review feedback be formatted?

Use a summary with files reviewed, issue count, and severity, then group findings into critical issues requiring fixes, important issues, suggestions, and positive observations. Each issue should include a file:line reference and an actionable fix.

What are common DDD and CQRS anti-patterns to flag in reviews?

Flag domain logic placed in validators instead of entity methods, bypassing the validation framework, direct JPA save calls without service-layer validation, and network IO inside repositories. Validators should enforce SHOULD rules while entities enforce CAN rules.

Does this review approach cover testing practices?

Yes, it checks for unit tests using JUnit 5, Mockito, and AssertJ, integration tests with @SpringBootTest and TestContainers where needed, proper mocking of dependencies, and updated OpenAPI specs when endpoints change.