sql-integrity-check
/sql-integrity-check
Review SQL queries and data-model changes for correctness, access scope, safe parameterization, and performance. Use when writing joins, filters, migrations, reports, or analytics queries.
- Author
- voyager67 ↗
- Repository
- AgentFieldkit ↗
- Licence
- MIT
- Last repository change
- 30.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review SQL queries and data-model changes for correctness, access scope, safe parameterization, and performance. Use when writing joins, filters, migrations, reports, or analytics queries.
Original author description
Review SQL queries and data-model changes for correctness, access scope, safe parameterization, and performance. Use when writing joins, filters, migrations, reports, or analytics queries.
How it works
- Procedure
- Deliverable
- Boundaries
SKILL.md preview
--- name: sql-integrity-check description: Review SQL queries and data-model changes for correctness, access scope, safe parameterization, and performance. Use when writing joins, filters, migrations, reports, or analytics queries. license: MIT --- # SQL Integrity Check ## Procedure 1. Identify the database engine, schema constraints, expected row grain, key relationships, indexes, and caller permissions. 2. For every query, state the intended output grain. Verify joins cannot silently multiply rows and filters preserve intended inclusions/exclusions. 3. Confirm user-controlled values are bound parameters, not concatenated into SQL. Review dynamic identifiers separately because they often need allowlists. 4. Check NULL semantics, timezone/date boundaries, numeric precision, collation, case sensitivity, pagination stability, and aggregate behavior. 5. Inspect query plans or EXPLAIN output on representative non-production data when performance matters. Avoid full table scans or expensive locks without understanding scale. 6. For migrations, verify constraints, backfill logic, idempotency, and compatibility with old/new application versions. 7. Test edge cases: no rows, duplicate keys, missing foreign keys, boundary dates, and values that could alter the query structure. ## Deliverable Explain expected row grain, correctness risks, access-control assumptions, relevant plan/index observations, and tests performed. ## Boundaries - Do not execute destructive statements or real-data exports without explicit authorization. - Do not expose customer rows or secrets in logs or examples. - Treat a fast query as incorrect if it returns the wrong entities or hides duplicates.
Versions
The database has no other skills named sql-integrity-check.
Database snapshot: 13.11.2026 · package version e5e5df314cbe (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100db-review
Reviews database schemas, queries, and migrations for correctness, performance, security, and best practices. Use when reviewing SQL migration files or when the user mentions database review, schema review, or query audit. - 100sql-quality-check
Check SQL files for MySQL performance problems (full table scans, ineffective joins, filesorts, functions on indexed columns, implicit conversions and more) and report them, CI style, without changing anything. Use when asked to check, lint or review the SQL of a project, or to… - 100fai-sql-code-review-skill
Review SQL code for correctness, performance, security, and maintainability across PostgreSQL, SQL Server, and MySQL. Use when auditing SQL in PRs or reviewing database migration scripts. - 100database-optimization
Optimize SQL queries, indexes, and identify N+1 problems. Use for database performance and migration review. - 90code-review
Review EF Core pull requests or local changes for concrete correctness, compatibility, performance, security, and test-coverage problems. Use when asked to review, critique, or check code changes before merge or submission. - 93exploratory-data-analysis
Use this skill when exploring an unfamiliar dataset, investigating data quality issues, validating data pipeline outputs before production use, reviewing SQL queries for correctness and performance, or producing a data quality scorecard for a data asset.