review-sql

Identify SQL injection, indexing, and transaction risks in code scopes.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-sql
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-sql
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/review-sql
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-sql

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review SQL and query constructs to identify injection risks, indexing issues, transaction boundaries, NULL handling, dialect portability, large-table access patterns, and sensitive column exposure; it outputs a structured findings list for remediation.

Core Features & Use Cases

  • Detect SQL injection risks, ensure proper parameterization, and flag unsafe string concatenation.
  • Identify missing indexes, suboptimal joins, and potentially expensive queries on large tables, with actionable recommendations.
  • Use in code reviews of projects containing SQL (raw SQL, embedded SQL, or ORM-generated SQL) to produce standardized findings for integration with code review workflows.

Quick Start

Provide a code scope containing SQL to receive a findings list.

Frequently Asked Questions about review-sql

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

FAQPage Schema
How do I review SQL code for injection risks and query performance issues?

SQL injection detection identifies unsafe string concatenation in raw or ORM-generated SQL and verifies proper parameterization. It flags these risks within a given code scope and outputs a structured findings list referencing specific file locations for remediation.

How do I check embedded SQL for missing indexes and large-table pagination issues?

Checking embedded SQL for missing indexes and large-table pagination issues involves analyzing query constructs against large-table access patterns. The process outputs a structured findings list with specific file location references to optimize suboptimal joins and expensive queries.

Can I scan ORM-generated SQL for transaction boundaries and NULL handling?

Yes, you can scan ORM-generated SQL for transaction boundaries and NULL handling. The analysis reviews query constructs to identify transaction boundary issues and NULL handling flaws, providing a standardized findings list referencing exact file locations.

What is the best way to identify sensitive column exposure in database queries?

The best way to identify sensitive column exposure in database queries is to review the SQL query constructs within the code scope. This detects sensitive column access and outputs a structured findings list referencing specific file locations for remediation.

Does SQL code review support dialect portability checks for database queries?

Yes, SQL code review supports dialect portability checks for database queries. It evaluates query constructs within raw SQL, embedded SQL, or ORM-generated SQL to identify dialect portability issues and outputs a structured findings list for remediation.