[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M796EM7FRJXC0RXY74AW2V3C":3,"skill-same:01M796EM7FRJXC0RXY74AW2V3C":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M796EM7FRJXC0RXY74AW2V3C","supabase-deploy-integration",null,"Deploy and manage Supabase projects in production. Covers database migrations,\nEdge Functions deployment, secrets management, zero-downtime rollouts,\nblue\u002Fgreen branching, rollback procedures, and post-deploy health checks.\nUse when deploying Supabase to production, running migrations, deploying\nEdge Functions, managing secrets, or implementing zero-downtime deployments.\nTrigger: \"deploy supabase\", \"supabase migration push\", \"deploy edge function\",\n\"supabase rollback\", \"supabase blue green\", \"supabase health check\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-deploy-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase-deploy-integration\ndescription: |\n  Deploy and manage Supabase projects in production. Covers database migrations,\n  Edge Functions deployment, secrets management, zero-downtime rollouts,\n  blue\u002Fgreen branching, rollback procedures, and post-deploy health checks.\n  Use when deploying Supabase to production, running migrations, deploying\n  Edge Functions, managing secrets, or implementing zero-downtime deployments.\n  Trigger: \"deploy supabase\", \"supabase migration push\", \"deploy edge function\",\n  \"supabase rollback\", \"supabase blue green\", \"supabase health check\".\nallowed-tools: Read, Write, Edit, Bash(npx:supabase), Bash(supabase:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, supabase, deployment, migrations, edge-functions, devops]\n---\n\n# Supabase Deploy Integration\n\n## Overview\n\nDeploy and manage Supabase projects in production with confidence. This skill covers the full deployment lifecycle: pushing database migrations, deploying Edge Functions, managing secrets, executing zero-downtime rollouts with blue\u002Fgreen database branching, rolling back failed migrations, and verifying deployment health. All commands use the Supabase CLI with `--project-ref` for explicit project targeting.\n\n**SDK**: `@supabase\u002Fsupabase-js` — [supabase.com\u002Fdocs](https:\u002F\u002Fsupabase.com\u002Fdocs)\n\n## Prerequisites\n\n- Supabase CLI installed (`npm install -g supabase` or `npx supabase`)\n- Supabase project linked (`npx supabase link --project-ref \u003Cyour-ref>`)\n- Database migrations in `supabase\u002Fmigrations\u002F` directory\n- Edge Functions in `supabase\u002Ffunctions\u002F` directory (if deploying functions)\n- `SUPABASE_ACCESS_TOKEN` set for CI\u002Fnon-interactive environments\n\n## Instructions\n\n### Step 1 — Push Database Migrations and Deploy Edge Functions\n\nApply pending database migrations to your production project, then deploy Edge Functions with their required secrets.\n\n**Database migrations:**\n\n```bash\n# Apply all pending migrations to production\nnpx supabase db push --project-ref $PROJECT_REF\n\n# Preview what will run without applying (dry run)\nnpx supabase db push --project-ref $PROJECT_REF --dry-run\n\n# Check current migration status\nnpx supabase migration list --project-ref $PROJECT_REF\n```\n\nEach migration file in `supabase\u002Fmigrations\u002F` is applied in timestamp order. The CLI tracks which migrations have already been applied and only runs new ones.\n\n**Edge Functions deployment:**\n\n```bash\n# Deploy a single Edge Function\nnpx supabase functions deploy process-webhook --project-ref $PROJECT_REF\n\n# Deploy all Edge Functions at once\nnpx supabase functions deploy --project-ref $PROJECT_REF\n```\n\n**Secrets management — set environment variables for Edge Functions:**\n\n```bash\n# Set individual secrets\nnpx supabase secrets set STRIPE_KEY=sk_live_xxx --project-ref $PROJECT_REF\nnpx supabase secrets set WEBHOOK_SECRET=whsec_xxx --project-ref $PROJECT_REF\n\n# Set multiple secrets at once\nnpx supabase secrets set API_KEY=value1 SIGNING_KEY=value2 --project-ref $PROJECT_REF\n\n# List current secrets (names only, values hidden)\nnpx supabase secrets list --project-ref $PROJECT_REF\n\n# Remove a secret\nnpx supabase secrets unset OLD_KEY --project-ref $PROJECT_REF\n```\n\n### Step 2 — Zero-Downtime Deployments and Blue\u002FGreen Branching\n\nUse Supabase database branching to test migrations against a production-like environment before cutting over.\n\n**Blue\u002Fgreen deployment via database branching:**\n\n```bash\n# Create a preview branch (clones schema, not data)\nnpx supabase branches create staging-v2 --project-ref $PROJECT_REF\n\n# The branch gets its own connection string and API URL\n# Test your migrations against the branch first\nnpx supabase db push --project-ref $BRANCH_REF\n\n# Verify the branch works with your application\n# Point a staging instance at the branch's connection string\n\n# When satisfied, merge branch changes into production\n# Apply the same migrations to the main project\nnpx supabase db push --project-ref $PROJECT_REF\n\n# Delete the branch after successful cutover\nnpx supabase branches delete staging-v2 --project-ref $PROJECT_REF\n```\n\n**Rolling deployment pattern for zero downtime:**\n\n1. Deploy backward-compatible migration first (additive schema changes only)\n2. Deploy application code that works with both old and new schema\n3. Run data backfill if needed\n4. Deploy cleanup migration (drop old columns\u002Ftables) after all instances updated\n\n```sql\n-- Migration 1: Add new column (backward compatible)\nALTER TABLE orders ADD COLUMN status_v2 text;\n\n-- Migration 2: Backfill (run separately, can be done in batches)\nUPDATE orders SET status_v2 = status WHERE status_v2 IS NULL;\n\n-- Migration 3: Cleanup (only after all app instances use status_v2)\nALTER TABLE orders DROP COLUMN status;\nALTER TABLE orders RENAME COLUMN status_v2 TO status;\n```\n\n### Step 3 — Rollback, Health Checks, and Monitoring\n\nWhen a migration fails or causes issues, roll it back. Then verify deployment health.\n\n**Rollback a failed migration:**\n\n```bash\n# Mark a specific migration as reverted (removes it from the applied list)\nnpx supabase migration repair --status reverted \u003Cmigration_version> --project-ref $PROJECT_REF\n\n# Example: revert migration 20260322120000\nnpx supabase migration repair --status reverted 20260322120000 --project-ref $PROJECT_REF\n\n# After marking as reverted, manually undo the schema changes\n# Write a new \"down\" migration to reverse the changes\nnpx supabase migration new rollback_order_status\n```\n\n```sql\n-- supabase\u002Fmigrations\u002F\u003Ctimestamp>_rollback_order_status.sql\n-- Reverse the changes from the failed migration\nALTER TABLE orders DROP COLUMN IF EXISTS status_v2;\n```\n\n```bash\n# Push the rollback migration\nnpx supabase db push --project-ref $PROJECT_REF\n```\n\n**Post-deploy health check:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\nasync function healthCheck() {\n  const supabase = createClient(\n    process.env.SUPABASE_URL!,\n    process.env.SUPABASE_ANON_KEY!\n  )\n\n  const checks = {\n    database: false,\n    auth: false,\n    storage: false,\n    functions: false,\n  }\n\n  \u002F\u002F Database connectivity\n  const dbStart = Date.now()\n  const { error: dbErr } = await supabase.from('_health').select('count').limit(1)\n  checks.database = !dbErr || dbErr.code === 'PGRST116' \u002F\u002F table not found is OK\n  const dbLatency = Date.now() - dbStart\n\n  \u002F\u002F Auth service\n  const { error: authErr } = await supabase.auth.getSession()\n  checks.auth = !authErr\n\n  \u002F\u002F Storage service\n  const { error: storageErr } = await supabase.storage.listBuckets()\n  checks.storage = !storageErr\n\n  \u002F\u002F Edge Function ping (replace with your function name)\n  try {\n    const { error: fnErr } = await supabase.functions.invoke('health-ping')\n    checks.functions = !fnErr\n  } catch {\n    checks.functions = false\n  }\n\n  const allHealthy = Object.values(checks).every(Boolean)\n\n  console.log({\n    status: allHealthy ? 'healthy' : 'degraded',\n    checks,\n    db_latency_ms: dbLatency,\n    timestamp: new Date().toISOString(),\n  })\n\n  return allHealthy\n}\n```\n\n**Monitoring via Supabase Dashboard:**\n\n- Navigate to **Dashboard > Reports** for database performance metrics\n- Check **Dashboard > Logs > Postgres** for slow queries and errors\n- Review **Dashboard > Logs > Edge Functions** for function invocation logs\n- Set up **Dashboard > Database > Webhooks** for change notifications\n- Monitor **Dashboard > Settings > Infrastructure** for resource utilization\n\n## Output\n\nAfter completing these steps, you will have:\n\n- All pending database migrations applied to production via `supabase db push`\n- Edge Functions deployed to Supabase's global edge network\n- Secrets configured for Edge Functions without exposing values in code\n- A zero-downtime deployment strategy using database branching or rolling migrations\n- Rollback capability for any failed migration via `migration repair --status reverted`\n- Health check endpoint verifying database, auth, storage, and function connectivity\n- Monitoring configured through the Supabase Dashboard Reports\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `migration already applied` | Re-running a migration that succeeded | Check `npx supabase migration list` — skip if already applied |\n| `permission denied for schema` | Migration modifies a protected schema | Use `ALTER DEFAULT PRIVILEGES` or run via dashboard SQL editor |\n| `functions deploy: not linked` | Project not linked locally | Run `npx supabase link --project-ref $PROJECT_REF` first |\n| `secret already exists` | Setting a secret that exists | `supabase secrets set` overwrites by default — this is safe |\n| `branch limit reached` | Too many active branches | Delete unused branches with `supabase branches delete` |\n| `migration repair` has no effect | Wrong version number | Run `supabase migration list` to find the exact version string |\n| `connection refused` on db push | IP not allowlisted | Add your IP in Dashboard > Settings > Database > Network Bans |\n| Edge Function 500 after deploy | Missing secret or import error | Check `supabase functions logs \u003Cname>` for stack trace |\n\n## Examples\n\n**CI\u002FCD pipeline — GitHub Actions:**\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\nname: Deploy to Supabase\non:\n  push:\n    branches: [main]\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: supabase\u002Fsetup-cli@v1\n        with:\n          version: latest\n\n      - name: Link project\n        run: npx supabase link --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}\n        env:\n          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}\n\n      - name: Push migrations\n        run: npx supabase db push --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}\n        env:\n          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}\n\n      - name: Deploy Edge Functions\n        run: npx supabase functions deploy --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}\n        env:\n          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}\n```\n\n**Quick rollback script:**\n\n```bash\n#!\u002Fbin\u002Fbash\n# rollback.sh — Revert the last migration\nset -euo pipefail\n\nREF=\"${1:?Usage: rollback.sh \u003Cproject-ref>}\"\nLAST=$(npx supabase migration list --project-ref \"$REF\" 2>\u002Fdev\u002Fnull | tail -1 | awk '{print $1}')\n\necho \"Reverting migration: $LAST\"\nnpx supabase migration repair --status reverted \"$LAST\" --project-ref \"$REF\"\necho \"Migration $LAST marked as reverted. Write and push a compensating migration next.\"\n```\n\n## Resources\n\n- [Database Migrations Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fdatabase-migrations)\n- [Edge Functions Deployment](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Fdeploy)\n- [Supabase CLI Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fcli)\n- [Database Branching](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fbranching)\n- [Secrets Management](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Fsecrets)\n- [Supabase Dashboard Reports](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fplatform\u002Freports)\n\n## Next Steps\n\n- For schema design from requirements, see `supabase-schema-from-requirements`\n- For RLS policy configuration, see `supabase-policy-guardrails`\n- For webhook and event handling, see `supabase-webhooks-events`\n- For production readiness checklist, see `supabase-prod-checklist`\n- For multi-environment setup, see `supabase-multi-env-setup`\n","# Supabase Deploy Integration\n\n## Overview\n\nDeploy and manage Supabase projects in production with confidence. This skill covers the full deployment lifecycle: pushing database migrations, deploying Edge Functions, managing secrets, executing zero-downtime rollouts with blue\u002Fgreen database branching, rolling back failed migrations, and verifying deployment health. All commands use the Supabase CLI with `--project-ref` for explicit project targeting.\n\n**SDK**: `@supabase\u002Fsupabase-js` — [supabase.com\u002Fdocs](https:\u002F\u002Fsupabase.com\u002Fdocs)\n\n## Prerequisites\n\n- Supabase CLI installed (`npm install -g supabase` or `npx supabase`)\n- Supabase project linked (`npx supabase link --project-ref \u003Cyour-ref>`)\n- Database migrations in `supabase\u002Fmigrations\u002F` directory\n- Edge Functions in `supabase\u002Ffunctions\u002F` directory (if deploying functions)\n- `SUPABASE_ACCESS_TOKEN` set for CI\u002Fnon-interactive environments\n\n## Instructions\n\n### Step 1 — Push Database Migrations and Deploy Edge Functions\n\nApply pending database migrations to your production project, then deploy Edge Functions with their required secrets.\n\n**Database migrations:**\n\n```bash\n# Apply all pending migrations to production\nnpx supabase db push --project-ref $PROJECT_REF\n\n# Preview what will run without applying (dry run)\nnpx supabase db push --project-ref $PROJECT_REF --dry-run\n\n# Check current migration status\nnpx supabase migration list --project-ref $PROJECT_REF\n```\n\nEach migration file in `supabase\u002Fmigrations\u002F` is applied in timestamp order. The CLI tracks which migrations have already been applied and only runs new ones.\n\n**Edge Functions deployment:**\n\n```bash\n# Deploy a single Edge Function\nnpx supabase functions deploy process-webhook --project-ref $PROJECT_REF\n\n# Deploy all Edge Functions at once\nnpx supabase functions deploy --project-ref $PROJECT_REF\n```\n\n**Secrets management — set environment variables for Edge Functions:**\n\n```bash\n# Set individual secrets\nnpx supabase secrets set STRIPE_KEY=sk_live_xxx --project-ref $PROJECT_REF\nnpx supabase secrets set WEBHOOK_SECRET=whsec_xxx --project-ref $PROJECT_REF\n\n# Set multiple secrets at once\nnpx supabase secrets set API_KEY=value1 SIGNING_KEY=value2 --project-ref $PROJECT_REF\n\n# List current secrets (names only, values hidden)\nnpx supabase secrets list --project-ref $PROJECT_REF\n\n# Remove a secret\nnpx supabase secrets unset OLD_KEY --project-ref $PROJECT_REF\n```\n\n### Step 2 — Zero-Downtime Deployments and Blue\u002FGreen Branching\n\nUse Supabase database branching to test migrations against a production-like environment before cutting over.\n\n**Blue\u002Fgreen deployment via database branching:**\n\n```bash\n# Create a preview branch (clones schema, not data)\nnpx supabase branches create staging-v2 --project-ref $PROJECT_REF\n\n# The branch gets its own connection string and API URL\n# Test your migrations against the branch first\nnpx supabase db push --project-ref $BRANCH_REF\n\n# Verify the branch works with your application\n# Point a staging instance at the branch's connection string\n\n# When satisfied, merge branch changes into production\n# Apply the same migrations to the main project\nnpx supabase db push --project-ref $PROJECT_REF\n\n# Delete the branch after successful cutover\nnpx supabase branches delete staging-v2 --project-ref $PROJECT_REF\n```\n\n**Rolling deployment pattern for zero downtime:**\n\n1. Deploy backward-compatible migration first (additive schema changes only)\n2. Deploy application code that works with both old and new schema\n3. Run data backfill if needed\n4. Deploy cleanup migration (drop old columns\u002Ftables) after all instances updated\n\n```sql\n-- Migration 1: Add new column (backward compatible)\nALTER TABLE orders ADD COLUMN status_v2 text;\n\n-- Migration 2: Backfill (run separately, can be done in batches)\nUPDATE orders SET status_v2 = status WHERE status_v2 IS NULL;\n\n-- Migration 3: Cleanup (only after all app instances use status_v2)\nALTER TABLE orders DROP COLUMN status;\nALTER TABLE orders RENAME COLUMN status_v2 TO status;\n```\n\n### Step 3 — Rollback, Health Checks, and Monitoring\n\nWhen a migration fails or causes issues, roll it back. Then verify deployment health.\n\n**Rollback a failed migration:**\n\n```bash\n# Mark a specific migration as reverted (removes it from the applied list)\nnpx supabase migration repair --status reverted \u003Cmigration_version> --project-ref $PROJECT_REF\n\n# Example: revert migration 20260322120000\nnpx supabase migration repair --status reverted 20260322120000 --project-ref $PROJECT_REF\n\n# After marking as reverted, manually undo the schema changes\n# Write a new \"down\" migration to reverse the changes\nnpx supabase migration new rollback_order_status\n```\n\n```sql\n-- supabase\u002Fmigrations\u002F\u003Ctimestamp>_rollback_order_status.sql\n-- Reverse the changes from the failed migration\nALTER TABLE orders DROP COLUMN IF EXISTS status_v2;\n```\n\n```bash\n# Push the rollback migration\nnpx supabase db push --project-ref $PROJECT_REF\n```\n\n**Post-deploy health check:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\nasync function healthCheck() {\n  const supabase = createClient(\n    process.env.SUPABASE_URL!,\n    process.env.SUPABASE_ANON_KEY!\n  )\n\n  const checks = {\n    database: false,\n    auth: false,\n    storage: false,\n    functions: false,\n  }\n\n  \u002F\u002F Database connectivity\n  const dbStart = Date.now()\n  const { error: dbErr } = await supabase.from('_health').select('count').limit(1)\n  checks.database = !dbErr || dbErr.code === 'PGRST116' \u002F\u002F table not found is OK\n  const dbLatency = Date.now() - dbStart\n\n  \u002F\u002F Auth service\n  const { error: authErr } = await supabase.auth.getSession()\n  checks.auth = !authErr\n\n  \u002F\u002F Storage service\n  const { error: storageErr } = await supabase.storage.listBuckets()\n  checks.storage = !storageErr\n\n  \u002F\u002F Edge Function ping (replace with your function name)\n  try {\n    const { error: fnErr } = await supabase.functions.invoke('health-ping')\n    checks.functions = !fnErr\n  } catch {\n    checks.functions = false\n  }\n\n  const allHealthy = Object.values(checks).every(Boolean)\n\n  console.log({\n    status: allHealthy ? 'healthy' : 'degraded',\n    checks,\n    db_latency_ms: dbLatency,\n    timestamp: new Date().toISOString(),\n  })\n\n  return allHealthy\n}\n```\n\n**Monitoring via Supabase Dashboard:**\n\n- Navigate to **Dashboard > Reports** for database performance metrics\n- Check **Dashboard > Logs > Postgres** for slow queries and errors\n- Review **Dashboard > Logs > Edge Functions** for function invocation logs\n- Set up **Dashboard > Database > Webhooks** for change notifications\n- Monitor **Dashboard > Settings > Infrastructure** for resource utilization\n\n## Output\n\nAfter completing these steps, you will have:\n\n- All pending database migrations applied to production via `supabase db push`\n- Edge Functions deployed to Supabase's global edge network\n- Secrets configured for Edge Functions without exposing values in code\n- A zero-downtime deployment strategy using database branching or rolling migrations\n- Rollback capability for any failed migration via `migration repair --status reverted`\n- Health check endpoint verifying database, auth, storage, and function connectivity\n- Monitoring configured through the Supabase Dashboard Reports\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `migration already applied` | Re-running a migration that succeeded | Check `npx supabase migration list` — skip if already applied |\n| `permission denied for schema` | Migration modifies a protected schema | Use `ALTER DEFAULT PRIVILEGES` or run via dashboard SQL editor |\n| `functions deploy: not linked` | Project not linked locally | Run `npx supabase link --project-ref $PROJECT_REF` first |\n| `secret already exists` | Setting a secret that exists | `supabase secrets set` overwrites by default — this is safe |\n| `branch limit reached` | Too many active branches | Delete unused branches with `supabase branches delete` |\n| `migration repair` has no effect | Wrong version number | Run `supabase migration list` to find the exact version string |\n| `connection refused` on db push | IP not allowlisted | Add your IP in Dashboard > Settings > Database > Network Bans |\n| Edge Function 500 after deploy | Missing secret or import error | Check `supabase functions logs \u003Cname>` for stack trace |\n\n## Examples\n\n**CI\u002FCD pipeline — GitHub Actions:**\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\nname: Deploy to Supabase\non:\n  push:\n    branches: [main]\n\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: supabase\u002Fsetup-cli@v1\n        with:\n          version: latest\n\n      - name: Link project\n        run: npx supabase link --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}\n        env:\n          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}\n\n      - name: Push migrations\n        run: npx supabase db push --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}\n        env:\n          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}\n\n      - name: Deploy Edge Functions\n        run: npx supabase functions deploy --project-ref ${{ secrets.SUPABASE_PROJECT_REF }}\n        env:\n          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}\n```\n\n**Quick rollback script:**\n\n```bash\n#!\u002Fbin\u002Fbash\n# rollback.sh — Revert the last migration\nset -euo pipefail\n\nREF=\"${1:?Usage: rollback.sh \u003Cproject-ref>}\"\nLAST=$(npx supabase migration list --project-ref \"$REF\" 2>\u002Fdev\u002Fnull | tail -1 | awk '{print $1}')\n\necho \"Reverting migration: $LAST\"\nnpx supabase migration repair --status reverted \"$LAST\" --project-ref \"$REF\"\necho \"Migration $LAST marked as reverted. Write and push a compensating migration next.\"\n```\n\n## Resources\n\n- [Database Migrations Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fdatabase-migrations)\n- [Edge Functions Deployment](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Fdeploy)\n- [Supabase CLI Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fcli)\n- [Database Branching](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fbranching)\n- [Secrets Management](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Fsecrets)\n- [Supabase Dashboard Reports](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fplatform\u002Freports)\n\n## Next Steps\n\n- For schema design from requirements, see `supabase-schema-from-requirements`\n- For RLS policy configuration, see `supabase-policy-guardrails`\n- For webhook and event handling, see `supabase-webhooks-events`\n- For production readiness checklist, see `supabase-prod-checklist`\n- For multi-environment setup, see `supabase-multi-env-setup`\n",{"name":5,"tags":24,"author":31,"license":15,"version":32,"description":33,"allowed-tools":34,"compatible-with":35},[25,26,27,28,29,30],"saas","supabase","deployment","migrations","edge-functions","devops","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Deploy and manage Supabase projects in production. Covers database migrations,\nEdge Functions deployment, secrets management, zero-downtime rollouts,\nblue\u002Fgreen branching, rollback procedures, and post-deploy health checks.\nUse when deploying Supabase to production, running migrations, deploying\nEdge Functions, managing secrets, or implementing zero-downtime deployments.\nTrigger: \"deploy supabase\", \"supabase migration push\", \"deploy edge function\",\n\"supabase rollback\", \"supabase blue green\", \"supabase health check\".\n","Read, Write, Edit, Bash(npx:supabase), Bash(supabase:*), Bash(curl:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--supabase-pack--supabase-deploy-integration",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill supabase-deploy-integration",{"tool":51,"command":52},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill supabase-deploy-integration",{"tool":54,"command":55},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill supabase-deploy-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-deploy-integration\u002FSKILL.md",true,[],[60,67,74,81,88,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]