AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Db Migration

skill-nikandr-surkov-ai-saas-starter-db-migration · by nikandr-surkov

Make a database schema change safely — edit schema.ts, generate the migration, review the SQL, apply it. Use for any change under src/db/.

↗ Website ↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-nikandr-surkov-ai-saas-starter-db-migration

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-nikandr-surkov-ai-saas-starter-db-migration)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 17d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Db Migration? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Database migration

Applied migrations are immutable history. This skill exists so nobody ever "just edits the SQL file".

Steps

  1. Ask the user first. Schema changes are on the ASK FIRST list in

AGENTS.md. Describe the change and why.

  1. Edit src/db/schema.ts only. Conventions:
  • Every foreign key gets an index.
  • Timestamps: createdAt with defaultNow(), timezone-aware.
  • Money in integer cents; credits in integers.
  • Enums via pgEnum, named _.
  1. Generate: pnpm db:generate. Never write migration SQL by hand.
  2. Read the generated file in drizzle/. Confirm: no unintended

DROP, correct column types/defaults, indexes present. Column renames often generate drop+create — if data must survive, say so and write the migration plan out for the user before applying.

  1. Apply locally: pnpm db:migrate (Postgres running via

docker compose up -d).

  1. Run pnpm test — the ledger suite will catch schema drift in credit

tables.

  1. Commit src/db/schema.ts and the new drizzle/ files together.

Never

  • Edit or delete an existing file in drizzle/.
  • Run drizzle-kit push against anything but a throwaway local DB —

this repo uses generated, committed migrations.

  • Touch credit_transactions semantics (signed integer amounts, UNIQUE

idempotencyKey) without reading .claude/rules/billing.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Databases