Review SQL queries for tenant_id scoping, parameterization, and safe timestamp usage.
npx skills add https://github.com/anotherben/claude-harness --skill sql-guard
Please help me install this Agent Skill. Skill: sql-guard Source: https://github.com/anotherben/claude-harness/tree/main/skills/sql-guard Command: npx skills add https://github.com/anotherben/claude-harness --skill sql-guard
This Skill helps prevent tenant isolation breaches and unsafe SQL patterns by guiding developers to follow strict tenant_id scoping, parameterization, and safe timestamp usage before writing or editing queries or migrations.
Run the SQL Guard prior to writing or editing queries to ensure tenant isolation, parameterization, and safe timestamp usage.
High-intent search queries and answers about installing and using this skill.
Preventing tenant isolation breaches requires enforcing strict tenant_id scoping on all tenant-scoped tables in your SQL queries. This involves verifying that every insert, update, delete, and complex join includes proper tenant_id parameterization to avoid cross-table data leakage.
Safe SQL patterns for database migrations include using parameterized queries and type-safe joins to prevent cross-table data leakage. Following safe migration practices ensures tenant_id scoping and proper timestamp handling remain intact during schema changes.
Reviewing SQL code for tenant_id scoping requires reading the schema reference and following strict guidelines to verify tenant_id inclusion, parameterization, and proper timestamp handling across all database interactions including inserts, updates, deletes, and complex joins.
Tenant data leaks across tables when SQL queries lack proper tenant_id scoping and parameterization. Unsafe query construction in complex joins and missing tenant_id enforcement in inserts, updates, or deletes cause cross-table data leakage in multi-tenant systems.
Parameterized queries are required to prevent cross-table data leakage and ensure tenant isolation. They enforce safe query construction by binding parameters securely, which stops unsafe SQL patterns and protects tenant-scoped data from exposure.
Before writing tenant-scoped queries, you should check for tenant_id scoping on all tenant-scoped tables, parameterized query construction, type-safe joins, and proper timestamp handling. Verifying these patterns prevents tenant isolation breaches and unsafe data leakage.
marquesfelipEnforce tenant_id scoping across tenant-related tables in single-database SaaS applications.
Buntyarora97Automate PostgreSQL database creation, status checks, and safe SQL execution.
NoobyGainsEnforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.
baleen37Replace arbitrary setTimeout calls with condition polling in tests.
