home / skills / jeremylongshore / claude-code-plugins-plus-skills / supabase-prod-checklist

This skill helps you execute and verify a Supabase production deployment, ensuring health checks, monitoring, and rollback readiness.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill supabase-prod-checklist

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.1 KB
---
name: supabase-prod-checklist
description: |
  Execute Supabase production deployment checklist and rollback procedures.
  Use when deploying Supabase integrations to production, preparing for launch,
  or implementing go-live procedures.
  Trigger with phrases like "supabase production", "deploy supabase",
  "supabase go-live", "supabase launch checklist".
allowed-tools: Read, Bash(kubectl:*), Bash(curl:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Supabase Prod Checklist

## Prerequisites
- Staging environment tested and verified
- Production API keys available
- Deployment pipeline configured
- Monitoring and alerting ready


See `{baseDir}/references/implementation.md` for detailed implementation guide.

## Output
- Deployed Supabase integration
- Health checks passing
- Monitoring active
- Rollback procedure documented

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources
- [Supabase Status](https://status.supabase.com)
- [Supabase Support](https://supabase.com/docs/support)

Overview

This skill executes a Supabase production deployment checklist and coordinates rollback procedures to ensure safe go-live. It codifies staging validation, secret management, deployment gate checks, monitoring activation, and documented rollback steps. Use it to reduce deployment risk and standardize launch outcomes for Supabase-backed apps.

How this skill works

The skill inspects pre-deployment prerequisites (staging verification, production API keys, pipeline readiness) and runs a sequence of health and smoke checks after deployment. It validates monitoring and alerting, confirms data and auth flows, and produces a concise deployment report. If critical failures are detected, it guides and documents an immediate rollback procedure and post-rollback verification.

When to use it

  • Preparing to push Supabase changes from staging to production
  • Running final go-live checks before a product launch
  • Validating production API keys, secrets, and pipeline configuration
  • Activating monitoring and alerting for a new Supabase integration
  • Executing an emergency rollback after a failed deployment

Best practices

  • Complete a full staging test cycle and record results before production
  • Store and rotate production API keys in a secure secrets manager
  • Ensure CI/CD pipeline has immutable build artifacts and version tags
  • Enable end-to-end monitoring and set practical alert thresholds
  • Document rollback steps and test them periodically in a sandbox

Example use cases

  • Run the checklist as a pre-launch gate when promoting a staging branch to main
  • Validate authentication and row-level security after migrating schemas
  • Confirm real-time subscriptions and storage access work under production load
  • Trigger rollback guidance when a deployment causes API errors or data regressions
  • Prep a deployment report to share with stakeholders after go-live

FAQ

What are the must-have prerequisites?

At minimum, confirm a verified staging run, accessible production API keys, a configured deployment pipeline, and active monitoring/alerts.

How does rollback get triggered?

Rollback is triggered when critical health checks or core functionality tests fail; the skill provides documented steps and verification checks to restore the previous stable release.

Can this be integrated into CI/CD?

Yes. The checklist maps to CI/CD gates and can be run automatically as pre- or post-deployment jobs, while rollbacks can be invoked through the pipeline.