Analyzes SQL queries for risk factors and safer execution strategies.
npx skills add https://github.com/winhok/testkit --skill sql-safety-review
Please help me install this Agent Skill. Skill: sql-safety-review Source: https://github.com/winhok/testkit/tree/main/skills/sql-safety-review Command: npx skills add https://github.com/winhok/testkit --skill sql-safety-review
评估 SQL SELECT 查询是否存在炸库风险（全表扫描、大范围扫描、排序/临时表开销），并给出更安全的改写方案，同时引导用户通过 EXPLAIN 与表结构信息进行精确诊断。当用户贴出SQL问“能不能跑”时，也应触发。
请对给定的 SELECT SQL 进行初步风险评估，提出安全改写与 EXPLAIN 指引。
High-intent search queries and answers about installing and using this skill.
To check if a SQL SELECT query is safe, perform a static risk assessment to identify full-table scans, broad range scans, and expensive sorts, ensuring your query avoids overwhelming the database.
The best way to rewrite a SQL query to prevent full-table scans is to narrow the scanning range, limit returned fields, and apply pagination, directly reducing the query's operational footprint.
Use EXPLAIN to diagnose expensive SQL sorts by providing the execution plan output, which reveals temporary table overhead and index hits for precise, progressive query analysis.
Your SQL query requires table structures and EXPLAIN output for precise diagnosis because static analysis alone cannot fully confirm index utilization without seeing the actual execution plan and schema.
Yes, you can get a safety review for SQL queries with complex JOINs and broad range scans by applying static analysis to detect risk signals and providing safer execution strategies.
RepairYourTechDefine TypeScript schemas and build type-safe SQL queries with Drizzle ORM.
rnavarychAnalyze execution plans and recommend index strategies across PostgreSQL, MySQL, MongoDB, and ClickHouse.
mwathibenOptimizes slow SQL queries using indexing strategies and EXPLAIN plan analysis.
Archive228Reviews SQL and ORM queries for injection risks, missing indexes, and bottlenecks.
