agentsclimarketplace

Nestjs database

Skill FilippoDeSilva/skills/skills/nestjs/nestjs-database

Skills for my agentic development workflow.

Install
npx -y skills add FilippoDeSilva/skills --skill nestjs-database

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implement data access patterns, Scaling, Migrations, and ORM selection in NestJS. Use when implementing TypeORM/Prisma repositories, migrations, or database patterns in NestJS.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 506 tokens by cl100k_base, as published. Nobody here has run it

NestJS Database Standards

Priority: P0 (FOUNDATIONAL)

Selection Strategy

See references/persistence_strategy.md for database selection matrix and scaling patterns (Connection Pooling, Sharding).

Patterns

  • Repository Pattern: Isolate database logic.
  • TypeORM: Inject @InjectRepository(Entity).
  • Prisma: Create comprehensive PrismaService.
  • Abstraction: Services should call Repositories, not raw SQL queries.

Configuration (TypeORM)

  • Async Loading: Always use TypeOrmModule.forRootAsync to load secrets from ConfigService.
  • Sync: Set synchronize: false in production; use migrations instead.

Migrations

  • Never use synchronize: true in production.
  • Generation: Whenever TypeORM entity (.entity.ts) modified, migration MUST generated using pnpm migration:generate.
  • Audit: Always inspect generated migration file to ensure it matches entity changes before applying.
  • Production Strategies:
  • CI/CD Integration (Recommended): Run pnpm migration:run in pre-deploy or post-deploy job (e.g., GitHub Actions, GitLab CI). Ensure production environment variables correctly set.
  • Manual SQL (For restricted DB access): Use typeorm migration:show to get SQL or simply copy up method's SQL into management tool (like Supabase SQL Editor). Always track manual runs in migrations metadata table.
  • Zero-Downtime: Use Expand-Contract pattern (Add -> Backfill -> Drop) for destructive changes.
  • Seeding: Use factories for dev data; only static dicts for prod.

Best Practices

  1. Pagination: Mandatory. Use limit/offset or cursor-based pagination.
  2. Indexing: Define indexes in code (decorators/schema) for frequently filtered columns (where, order by).
  3. Transactions: Use QueryRunner (TypeORM) or $transaction (Prisma) for all multi-step mutations to ensure atomicity.

Anti-Patterns

  • No synchronize in production: Use explicit migrations; synchronize: true drops and recreates columns.
  • No raw entity returns from services: Map to DTOs before leaving service layer.
  • No unpaginated list queries: All list endpoints must implement limit/offset or cursor pagination.

What ships with it: 2 files

2.9 KB alongside SKILL.md

evals/

references/

Gives 0 of the 12 instructions most databases sql skills give in 506 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

  • Use parameterized queriesin 37 of 589, across 34 files
  • Use timestamptz for timestampsin 30 of 589, across 14 files
  • Index foreign keysin 29 of 589, across 18 files
  • Create indexes concurrentlyin 29 of 589, across 24 files
  • Use numeric type for moneyin 25 of 589, across 8 files
  • Use cursor pagination instead of offsetin 24 of 589, across 17 files
  • Select only required columnsin 24 of 589, across 20 files
  • Add indexes manually on foreign key columnsin 22 of 589, across 12 files
  • Normalize to third normal formin 19 of 589, across 10 files
  • Configure connection poolingin 19 of 589, across 17 files
  • Put equality columns before range columns in indexesin 18 of 589, across 10 files
  • Read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

  • call repositories from services instead of raw SQL
  • use async loading for TypeORM configuration
  • inspect generated migration files before applying
  • define database indexes in code
  • use transactions for all multi-step mutations
  • map database entities to DTOs before leaving service layer

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.