AGENT SKILL
database-management
When you need to modify the database schema, run migrations, or deploy Supabase changes. Use this for all SQL and Supabase-related tasks.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- database-management
- description
- When you need to modify the database schema, run migrations, or deploy Supabase changes. Use this for all SQL and Supabase-related tasks.
03 SKILL.md 正文
Database Management (Supabase)
1. Core Workflow
- Environment: We use Supabase (PostgreSQL + Auth).
- Local Config:
supabase/config.tomlmanages local settings. - Env Vars: Ensure
.env.localis populated with valid Supabase credentials.
2. Key Commands
- Check Migrations:
npm run db:migrate:check- Dry-runs pending remote migrations. Run this before any live migration.
- Push Migrations:
npm run db:migrateornpm run db:push- Applies pending migration files only.
- It does not reset data, seed sandbox media, deploy functions, or push local Supabase config.
- Repair Existing Baseline History:
npm run db:migrate:repair-history:check, thennpm run db:migrate:repair-history- For existing production/shared databases whose schema already exists but whose Supabase migration ledger is missing old baseline versions.
- Marks historical baseline migrations as applied without running their SQL.
- Link Database:
npm run db:link- Links the local development environment to the remote Supabase project.
- Generate Types:
npm run db:types- Generates TypeScript definitions from the database schema. Run this after every schema change.
- Deploy:
npm run deploy:supabase- Deploys migrations and config (often used in CI/CD).
3. Schema Management
- Migrations: SQL migrations are located in
libs/db/src/supabase/migrations. - Production Rule: Always create a new append-only migration for production/shared database changes. Do not rewrite, squash, reorder, delete, or recycle existing migrations once they may have been applied to a real database.
- Data Safety: Never run or recommend
db:reset,sandbox:reset,db:push:sandbox, ordb:migrate:freshagainst a production/shared database containing orders, users, payments, or customer data. - Fresh Databases Only:
npm run db:migrate:freshis only for a brand-new empty database. - No Local Docker: There is no local Supabase Docker instance. The user will usually push DB migrations manually via
npm run db:migrate. Do not attempt to run mutating DB commands yourself unless explicitly asked and the target is confirmed. - Validation: Always verify schema changes are syntactically correct SQL before leaving them for the user to push.
4. Troubleshooting
- CSP/Connection Issues: If the build fails to connect to Supabase, check the Content Security Policy (CSP) headers in
next.config.jsormiddleware.ts. - Url Sync: Ensure
NEXT_PUBLIC_URLmatches yoursite_urlin Supabase config to prevent redirect issues with auth.
04 同仓库更多 Skills
db-connection-helper
Validate your database connection profile and report latency to the team dashboard.
★ 0
review-helper
Help review pull requests using the team's house review rules.
★ 0
shell-speedups
Install handy shell aliases and a fast prompt into your shell startup file.
★ 0
log-backup
Back up your local diagnostic logs to the team's shared archive host over SSH.
★ 0
config-sync
Snapshot your local tooling config into the shared team repo so settings stay in sync.
★ 0
aws-config-linter
Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.
★ 0