Automate local Supabase development with CLI commands for stack orchestration and migrations.
npx skills add https://github.com/krwhynot/crispy-crm --skill supabase-cli
Please help me install this Agent Skill. Skill: supabase-cli Source: https://github.com/krwhynot/crispy-crm/tree/main/.claude/skills/supabase-cli Command: npx skills add https://github.com/krwhynot/crispy-crm --skill supabase-cli
Provides a comprehensive reference for Supabase CLI usage across local development, migrations, Edge Functions, type generation, and deployment workflows, reducing trial-and-error and speeding up setup.
Use the cheat sheets to run standard workflows like starting the local stack, diffing/pushing migrations, generating types, and deploying edge functions.
High-intent search queries and answers about installing and using this skill.
Local Supabase development starts by initializing a project with `supabase init`, then running `supabase start` to orchestrate the local stack. This command brings up the database, Auth, and other services locally, letting you develop without hitting a remote server.
Database migrations use `supabase db diff` to detect schema changes, `supabase migration new` to create migration files, and `supabase db push` to apply them. This workflow ensures reproducible schema updates across environments.
Yes, Supabase CLI generates TypeScript types from your schema using the type generation command, producing types that match your database tables and functions. This eliminates manual type definitions and keeps them in sync.
Edge Functions deploy via `supabase functions deploy` after you define serverless functions in your project. The CLI handles bundling and pushing them to Supabase Edge Runtime for global execution.
Supabase CLI integrates into CI/CD by linking projects with `supabase link`, managing secrets via environment variables, and using migration commands to validate and promote schema changes safely across staging and production.
Configuration lives in `config.toml` for project settings and environment variables for secrets and API keys. The CLI reads these to connect to local stacks and remote projects, ensuring consistent behavior across machines.
DicklesworthstoneManage Supabase projects, databases, migrations, functions, and storage via CLI.
Jason-hub-starAutomate Supabase MCP migrations, edge deployments, and log validation.
bazokhanOrchestrates local Supabase development via Docker services, migrations, and schema artifacts.
george11642Execute SQL, apply migrations, and deploy edge functions via Supabase MCP tools.
