Reviews SQL queries for correctness, performance and safety problems such as SELECT star, missing indexes, unbounded updates, implicit casts and injection risks. Use when the user asks to optimize a query, explain why a query is slow, or check SQL before it runs on production data.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
UPDATE or DELETE on real data.Safety first
UPDATE or DELETE without a WHERE clause. Ask for confirmation and suggest running a SELECT COUNT(*) with the same condition first.Correctness
NULL comparisons written with = instead of IS NULL.LEFT JOIN followed by a WHERE condition on the right table, which silently turns it into an inner join.GROUP BY that does not match the selected columns, and COUNT(column) used where COUNT(*) was meant.NOT IN with a subquery that can return NULL. Prefer NOT EXISTS.Performance
SELECT * on wide tables. List the columns that are used.WHERE (WHERE LOWER(email) = ...). Suggest an expression index or a different predicate.LIKE '%term') that cannot use an index.EXPLAIN output instead of guessing.OFFSET pagination on large tables. Suggest keyset pagination.ORDER BY without LIMIT on large results, and DISTINCT used to hide a bad join.EXPLAIN output was given, ask for it and say what to look for (sequential scans, row estimates far from actual rows).Input: DELETE FROM sessions WHERE created_at < now() - interval '30 days'
Review: valid, but deletes an unknown number of rows. Run SELECT COUNT(*) with the same condition first, delete
in batches if the count is large, and keep it inside a transaction until the result looks right.
If the schema is unknown, say which assumptions the review makes about indexes and types.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Runs a list of HTTP checks against a base URL from a JSON file and reports status codes, response time and body assertions. Use when the user asks whether an API is up, wants a smoke test after a deploy, or needs to verify that endpoints return what the docs promise.
The English summary is being prepared. Showing the original description.
Turns git log output into a grouped markdown changelog using conventional commit prefixes such as feat, fix and docs. Use when the user prepares a release, asks for release notes, or wants a summary of what changed between two tags.
The English summary is being prepared. Showing the original description.
Writes clear git commit messages in the conventional commits style from a diff or a description of the change. Use when the user asks for a commit message, wants to tidy up a message before pushing, or has staged changes and no wording yet.
The English summary is being prepared. Showing the original description.
Profiles a CSV file column by column, reporting inferred type, missing values, unique counts and min, max and mean for numeric columns. Use when the user hands over a CSV and asks what is in it, whether the data is clean, or what to check before analysis.
The English summary is being prepared. Showing the original description.
Checks a Dockerfile for common problems such as unpinned base images, running as root, ADD instead of COPY, secrets in ENV or ARG and apt-get without cleanup. Use when the user asks to review, harden or slim down a Dockerfile.
The English summary is being prepared. Showing the original description.
Compares a .env file with its .env.example template and reports missing keys, undocumented extra keys, empty values and example files that contain real looking secrets. Use when the user asks why an app fails on startup with missing configuration, or wants to check environment files before committing.
The English summary is being prepared. Showing the original description.