java-reviewer

Exception handling review identifies silent failures in empty catch blocks, catch-all exceptions, and missing resource cleanup. The java-reviewer diagnoses these patterns and recommends try-with-resources adoption and meaningful error messages to strengthen robustness.

Yes. The java-reviewer detects raw types, unsafe null dereferences, and outdated patterns in legacy codebases, then recommends modern Java 17+ idioms including Optional for null safety and contemporary stream and collection patterns.

Automated review flags mutable static fields, improper resource lifecycle, missing null guards, stream inefficiencies, and exception-handling gaps. The java-reviewer runs on Maven or Gradle projects to surface critical issues during CI/CD and code review workflows.

Stream and collection review focuses on idiomatic usage patterns that balance readability with performance. The java-reviewer assesses your code against modern best practices and suggests concrete optimizations aligned with Java 17+ conventions.

Yes. The java-reviewer operates on Maven and Gradle projects, scanning src/main/java/** to detect idiom violations, resource leaks, exception handling flaws, and null safety gaps specific to your build configuration.

Catch-all exceptions (catch Exception or Throwable) mask failures and complicate debugging; specific exception handling preserves intent and enables targeted recovery. The java-reviewer recommends replacing catch-all patterns with precise, meaningful exception handling.