review-java-service

Analyze Java/Spring fintech diffs to report defects in money handling and transactions.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/sswapnil2/ai-config-fintech --skill review-java-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-java-service
Source: https://github.com/sswapnil2/ai-config-fintech/tree/main/skills/review-java-service
Command: npx skills add https://github.com/sswapnil2/ai-config-fintech --skill review-java-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps reviewers identify and fix fintech Java/Spring service defects by analyzing diffs between the main branch and HEAD, ensuring critical quality gates are enforced during PRs.

Core Features & Use Cases

  • Checks for money handling correctness (BigDecimal with HALF_EVEN) and correct numeric DB types.
  • Validates transactional boundaries, proper use of @Transactional, and audit-ability within business operations.
  • Flags N+1 query patterns, lazy-loaded collections, and risky JPA usage, plus native queries with parameters.
  • Reviews external calls, timeouts, resilience patterns, and idempotency considerations, including Redis and Mongo access.
  • Highlights logging of PII data and PCI-relevant issues, and identifies missing tests or migration concerns.

Quick Start

Run git diff main...HEAD to surface issues in the Java/Spring fintech service.

Frequently Asked Questions about review-java-service

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

FAQPage Schema
How do I review Java Spring Boot diffs for fintech transactional boundary defects?

To review Java Spring Boot diffs for fintech transactional boundaries, run git diff main...HEAD. This surfaces transactional correctness issues by validating proper @Transactional usage and audit-ability within business operations.

What is the correct way to handle BigDecimal money types in Spring Boot fintech services?

BigDecimal money types in Spring Boot fintech services must use HALF_EVEN rounding and correct numeric database types. Analyzing branch diffs enforces these guardrails to prevent financial calculation defects.

How do I detect N+1 queries and risky JPA lazy loading in Java service code reviews?

Detect N+1 queries and risky JPA lazy loading in Java service code reviews by analyzing main to HEAD diffs. This flags N+1 query patterns, lazy-loaded collections, and native queries with parameters to prevent performance degradation.

Does this code review process check for PII logging in Java fintech applications?

Yes, the code review process checks for PII logging in Java fintech applications by analyzing git diffs. It highlights logging of PII data and PCI-relevant issues to ensure sensitive financial data is not exposed in application logs.

Can I validate external call timeouts and Redis caching idempotency in Spring Boot code reviews?

Yes, you can validate external call timeouts, resilience patterns, and Redis caching idempotency in Spring Boot code reviews. The diff analysis reviews external calls, timeout requirements, and Redis and Mongo access for safe integration.

When should I run a fintech Java service code review for database migration and test coverage?

Run a fintech Java service code review for database migration and test coverage during pull requests. The diff analysis identifies missing tests and migration concerns, enforcing proper testing and migration hygiene before merging changes.