AL-JANEF/janef-forge / skills/engineering/database-integrity
database-integrity
VerifiedSchema design, migrations, transactions, indexes, query behavior, backfills, and tenant isolation or RLS. Treats every schema or migration change as high risk because deployed data already exists. Use for SQL, ORMs, data models, migration strategy, query performance, or data-integrity questions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| capability.json | config | 2.3 KB |
capability.json
View on GitHub{
"id": "database-integrity",
"name": "Database Integrity",
"version": "2.0.0",
"domain": "engineering",
"description": "Schema design, migrations, transactions, indexes, query behavior, backfills, and tenant isolation or RLS. Treats every schema or migration change as high risk because deployed data already exists. Use for SQL, ORMs, data models, migration strategy, query performance, or data-integrity questions.",
"triggers": [
"database",
"db",
"sql",
"postgres",
"postgresql",
"mysql",
"sqlite",
"schema",
"migration",
"migrations",
"migrate",
"table",
"tables",
"column",
"columns",
"index",
"indexes",
"indices",
"foreign key",
"foreign keys",
"constraint",
"constraints",
"transaction",
"transactions",
"n+1",
"orm",
"prisma",
"drizzle",
"sequelize",
"typeorm",
"sqlalchemy",
"query plan",
"explain analyze",
"rls",
"row level security",
"row-level security",
"backfill",
"seed data",
"data model",
"nullability",
"unique constraint",
"supabase",
"stored procedure",
"trigger",
"deadlock",
"isolation level",
"security definer",
"policy",
"database role",
"app role",
"tenants table",
"drop table",
"drop column",
"truncate"
],
"negative_triggers": [
"sql injection"
],
"risk_level": "high",
"context_cost": "small",
"requires": [],
"optional_with": [
"api-contracts",
"performance-scalability",
"testing-verification"
],
"conflicts_with": [],
"verification_requirements": [
"migration applied from zero and on representative data",
"constraint, concurrency, and rollback or forward-fix paths tested",
"query plans inspected for performance-sensitive production queries",
"RLS or tenant scoping verified with a denied cross-tenant query when relevant"
],
"supported_hosts": [
"claude-code",
"codex"
],
"references": [],
"status": "stable",
"responsibilities": [
"schema-and-migrations",
"transaction-semantics",
"query-integrity",
"tenant-data-isolation"
],
"priority": 62,
"provenance": [
"agent-engineering-stack 1.1.0 database-integrity",
"lean-code-engineer 0.1.0 modules/database",
"janefskills 1.2.0 engineering-standard (database discipline)"
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |