quarkus-panache-smells

To fix N+1 query issues in Quarkus Panache repositories, you must detect eager loading patterns and refactor repository methods to use projections or pagination-safe queries. This skill identifies these ORM smells and suggests concrete refactoring steps to optimize data access.

Common ORM code smells in Quarkus Panache include eager fetching, missing projections, N+1 query patterns, data overfetching, and pagination issues. These typically occur when reviewing PanacheRepository usage and can be resolved by applying targeted repository method refactors.

To prevent data overfetching with PanacheRepository, you should replace eager loading with targeted projections and pagination-safe queries. This skill guides you through diagnosing overfetching smells and applying efficient data access patterns via repository methods.

Yes, this refactoring approach specifically targets the Quarkus Panache Repository pattern. It analyzes PanacheRepository codebases to diagnose ORM smells like N+1 queries and missing projections, then guides changes directly through repository methods and projections.

You should refactor eager loading in Quarkus Panache when diagnosing N+1 queries, data overfetching, or pagination issues in your codebase. This skill detects these performance smells and recommends practical repository query patterns to ensure efficient data retrieval.