Standardize Drizzle database schemas and mutations with audit fields, soft delete, dual IDs, and pagination.
npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-db
Please help me install this Agent Skill. Skill: sk-db Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/sk-db Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-db
This Skill solves the inconsistency and fragility of database code by standardizing audit fields, soft-deletes, dual human/technical IDs, pagination, deletion eligibility, and the migration workflow so your Next.js/Drizzle projects behave predictably in production.
createdAt/createdBy/modifiedAt/modifiedBy via auditFields and documents how to populate them using the kit’s injected userId from server action wrappers.deletedAt/deletedBy with softDeleteFields and guarantees reads filter out deleted rows via notDeleted().generateHumanId, atomic sequence-based getNextHumanId, gap-resilient getNextHumanIdSeq, and race-safe withHumanIdRetry() including the required SAVEPOINT behavior when called inside a parent transaction.parsePaginationParams, buildPaginationSQL, and createCachedCount with revalidation tagging to prevent stale totals.canHardDeleteUser to prevent permanent deletion when downstream references exist.db:generate → review SQL → db:migrate, and read-only inspection via pnpm db:query.Use the sk-db helpers when creating new Drizzle schema files and mutations to ensure every table includes auditFields, applies softDeleteFields where appropriate, and uses the kit’s pagination, human-id, and migration conventions.
High-intent search queries and answers about installing and using this skill.
To enforce audit fields and soft delete in Drizzle ORM, use helper modules that add createdAt/createdBy and deletedAt/deletedBy columns to schema definitions, ensuring reads filter out deleted rows via a notDeleted() helper.
Generating race-safe human IDs in Postgres requires atomic sequence functions wrapped in a retry mechanism that uses SAVEPOINT behavior when called inside a parent transaction to handle sequence gaps safely.
Implement safe pagination by parsing parameters, building pagination SQL, and using a cached count function with revalidation tagging to prevent stale totals across your Next.js application database queries.
Yes, this database pattern approach requires a repeatable migration workflow: generate migration SQL, manually review the output, apply the migration, and perform read-only data inspection via a dedicated query runner.
You should prevent hard deletion of database rows in Postgres when downstream references exist, using eligibility checks that verify no dependent records are present before allowing permanent deletion.
No, populating audit fields requires using injected userId from server action wrappers to automatically track createdBy and modifiedBy values, ensuring consistent attribution across all database mutations.
legions-developerDefine PostgreSQL schemas and run type-safe queries with Drizzle ORM.
parisgroup-aiGenerate, inspect, and apply Drizzle ORM migrations in Docker-based monorepos.
aberrantCodeConfigure Next.js App Router projects with Supabase authentication and Drizzle ORM.
echarabatiDefine schemas, run type-safe queries, and manage migrations with Drizzle ORM and Neon Postgres.