iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
query-inspector can inspect SQL in changed code, infer some ORM-generated queries, and flag possible issues before you ship a change. It is a Claude Code plugin with separate skills for reviewing query risks and cataloging queries. Its reports are a code-review aid—not proof that every runtime query was found or that a query will perform well.
What query-inspector does
The plugin analyzes query-generating source and produces reports; it does not edit your project code. Its two skills serve different purposes:
tuning-reportexamines Git changes or a broader project scan, then reports potential concerns such as N+1 queries, missing index coverage, SQL dialect mismatches, and query anti-patterns. It also suggests possible fixes.inventory-reportbuilds a catalog of queries, including their bodies and reported index coverage. Use it to map queries, rather than to prioritize tuning findings.
That makes the choice depend on the task: use the tuning report to review query-related changes, or the inventory report to understand the project’s query landscape. The official repository documents both skills.
How it analyzes queries—and what its findings mean
query-inspector uses three possible information layers: static heuristics, schema context, and optional live-database EXPLAIN. Static analysis is the default and does not require database access. Schema files, entities, migrations, or a live schema can provide context for index-coverage checks. Live EXPLAIN is opt-in and can add execution-plan evidence. The project says it can degrade gracefully when schema or database information is unavailable.
#1 Best Overall
Explicit SQL is analyzed as written. For ORM or dynamic query code, the tool infers likely SQL and assigns confidence labels such as EXACT, INFERRED, or AMBIGUOUS. Those labels matter: an inference is not a guarantee of the SQL emitted at runtime, and dynamic query construction may not be fully reconstructable from source.
- Treat a reported risk as a prompt for review, not proof of a defect.
- Check ambiguous or high-impact queries against actual SQL and, where relevant, an execution plan.
- For Hibernate, the README points to SQL logging as one way to inspect emitted SQL.
Static inspection can surface potential problems before a commit, but it cannot establish that every runtime query has been found or predict performance by itself. The project’s documentation does not report a general accuracy rate, benchmark, or time-saved figure.
Choose the right workflow
Review query-generating changes
Run tuning-report against the Git changes when reviewing a commit or range. This narrows attention to code changes that may affect queries and is the natural fit for a pre-commit review.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteScan a project more broadly
The tuning skill also supports a broader scan for a one-off pass beyond the current changes. Use this when you want potential tuning findings across more of the codebase.
Build a query catalog
Choose inventory-report when the goal is to enumerate and inspect queries, rather than rank potential issues or receive tuning suggestions.
Supported frameworks and databases
The project’s primary validated focus is Kotlin and Java. Documented query sources include JPA-derived methods, @Query, QueryDSL, MyBatis, and native SQL; the creator’s launch article also names Kotlin JDSL. The creator’s description identifies Python Django and SQLAlchemy adapters as available but less thoroughly validated. Do not assume equal coverage across languages or frameworks.
For live database workflows, the repository names MySQL and PostgreSQL. Basic static analysis does not require a database connection; live analysis adds setup and operational considerations.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsInstall the Claude Code plugin
The repository documents this CLI installation sequence:
Best Value
claude plugin marketplace add jogakdal/query-inspector
claude plugin install query-inspector@query-inspector-marketplaceBasic use requires Git and Python; the repository says its runtime scripts use Python’s standard library. It also documents a setup script and a skill-copy installation option. Because plugin installation procedures and requirements can change, check the repository README for the current instructions before installing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to check before enabling database access
Database connectivity is optional. The repository documents guardrails that block host patterns containing prod, live, or production by default and restrict queries to SELECT and EXPLAIN. It recommends a host allowlist and a read-only database account, and says to keep connection URLs in environment variables or a .env file rather than committed configuration.
These are controls described by the project, not an independent security audit. Before connecting any database, inspect the configuration and safeguards in the version you install, confirm the target host, and use credentials with only the access needed for analysis.
Version, license, and evidence limits
The creator’s launch article, published October 6, 2026, identifies the project as version 1.0.0 at that time. That date-specific version statement does not establish the current version. The repository describes query-inspector as MIT licensed; commercial use is permitted subject to retaining the license and copyright notice.
Neither the repository documentation nor the launch article provides a named performance benchmark or accuracy rate. Sample report counts describe illustrative projects, not expected results for other codebases. Evaluate findings against the actual SQL and database behavior relevant to your application.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
