Skip to content

AL-JANEF/janef-forge / skills/engineering/database-integrity

database-integrity

Unverified

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.

Database Integrity

Schema and migration changes are high risk because deployed data already exists and cannot be re-run. Put durable invariants in constraints when the database can enforce them.

Model and invariants

  • Choose types, nullability, defaults, keys, and uniqueness from domain meaning, not sample data.
  • Preserve constraints, foreign keys, uniqueness, nullability semantics, transactions, and least privilege.
  • Make tenant or ownership boundaries explicit in every access path. In multi-tenant systems a missing tenant scope is a critical finding; where RLS exists, never bypass it with a privileged role to make a query work.

Queries and transactions

  • Parameterize every query. Treat ORM convenience as syntax, not proof of correct query count or transaction behavior.
  • Inspect plans with representative cardinality before adding indexes; account for write amplification and maintenance cost.
  • Keep transactions short; define isolation needs and lock ordering for concurrent writes.
  • Avoid N+1 access and unbounded reads; paginate with stable ordering.

Migrations

  • Design expand → migrate → contract phases for mixed application versions.
  • Separate schema change, backfill, validation, and cleanup when locks or data volume matter. Backfills need batching, idempotent retries, progress tracking, and production-load awareness.
  • Make migrations deploy-compatible, observable, and recoverable; define rollback or forward-fix.
  • Destructive migrations (drop, truncate, type narrowing, data deletion) require explicit authorization and staging. Never claim one is safe without backup and restore evidence appropriate to the environment.
  • Audit-log sensitive data changes (security-logging).

Verification

  • Apply the migration from zero and against representative data; run representative queries afterwards.
  • Test constraints, concurrent edge cases, upgrade and rollback/forward-fix paths.
  • Confirm explain plans and lock impact for performance-sensitive production queries.
  • For RLS, tenant scoping, or privilege changes: run a real database check that a cross-tenant or unprivileged access is denied, and show that removing the control makes that test fail.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 117kUpdated Claude CodeCodexUnverifiedInstall