Skip to content

fcakyon/claude-codex-settings / plugins/supabase-skills/skills/supabase-cli

supabase-cli

Flagged

This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.

FileKindSize
SKILL.mdskill md6.3 KB
references/commands/functions.mdmarkdown543 B
references/commands/gen.mdmarkdown594 B
references/commands/init.mdmarkdown682 B
references/commands/link.mdmarkdown626 B
references/commands/login.mdmarkdown695 B
references/commands/network-bans.mdmarkdown230 B
references/commands/projects.mdmarkdown477 B
references/commands/pull.mdmarkdown7.0 KB
references/commands/secrets.mdmarkdown476 B
references/commands/start.mdmarkdown850 B
references/commands/status.mdmarkdown432 B
references/commands/stop.mdmarkdown475 B
references/commands/vanity-subdomains.mdmarkdown149 B
references/config/diff.mdmarkdown2.3 KB
references/config/pull.mdmarkdown8.0 KB
references/config/push.mdmarkdown1.5 KB
references/db/advisors.mdmarkdown174 B
references/db/diff.mdmarkdown2.8 KB
references/db/dump.mdmarkdown926 B
references/db/lint.mdmarkdown1.0 KB
references/db/pull.mdmarkdown5.4 KB
references/db/push.mdmarkdown843 B
references/db/query.mdmarkdown337 B
references/db/reset.mdmarkdown1.3 KB
references/db/schema-declarative-generate.mdmarkdown1.5 KB
references/db/schema-declarative-sync.mdmarkdown413 B
references/domains/activate.mdmarkdown523 B
references/examples.yamlconfig16.1 KB
references/functions/new.mdmarkdown510 B
references/functions/serve.mdmarkdown1.9 KB
references/inspect/db-bloat.mdmarkdown1.3 KB
references/inspect/db-blocking.mdmarkdown1.2 KB
references/inspect/db-cache-hit.mdmarkdown1.3 KB
references/inspect/db-calls.mdmarkdown1.3 KB
references/inspect/db-index-sizes.mdmarkdown660 B
references/inspect/db-index-usage.mdmarkdown968 B
references/inspect/db-locks.mdmarkdown1.1 KB
references/inspect/db-long-running-queries.mdmarkdown1.0 KB
references/inspect/db-outliers.mdmarkdown1.9 KB
references/inspect/db-replication-slots.mdmarkdown1.3 KB
references/inspect/db-role-connections.mdmarkdown1.6 KB
references/inspect/db-seq-scans.mdmarkdown720 B
references/inspect/db-table-index-sizes.mdmarkdown627 B
references/inspect/db-table-record-counts.mdmarkdown636 B
references/inspect/db-table-sizes.mdmarkdown756 B
references/inspect/db-total-index-size.mdmarkdown272 B
references/inspect/db-total-table-sizes.mdmarkdown608 B
references/inspect/db-traffic-profile.mdmarkdown1.8 KB
references/inspect/db-unused-indexes.mdmarkdown923 B
references/inspect/db-vacuum-stats.mdmarkdown2.4 KB
references/migration/list.mdmarkdown722 B
references/migration/new.mdmarkdown376 B
references/migration/repair.mdmarkdown2.6 KB
references/migration/squash.mdmarkdown892 B
references/overview.mdmarkdown5.4 KB
references/test/db.mdmarkdown440 B

references/commands/pull.md

View on GitHub
# supabase-pull

Refreshes local project state from a linked Supabase project or branch in one step, instead of running `config pull`, `db pull`, `migration fetch`, and `functions download` individually. It runs four steps, always in this order: pull config into `supabase/config.toml`, optionally fetch the remote migration history table into `supabase/migrations`, pull the database schema into `supabase/migrations` (also updating that database's own migration history table), and download every Edge Function's source into `supabase/functions`. The order is fixed rather than parallel: the database step depends on `db.major_version` in the config file the first step may have just changed, and on the local migration history the second step may have just populated.

Pass `--project-ref` to target a specific project, or the name (or UUID) of a branch of the currently linked project — values that are exactly 20 lowercase letters are always treated as project refs. Without it, the linked project is the target. `--remote-label` overrides the `[remotes.*]` block the config step would otherwise reuse or create for that target, identically to `config pull`'s own flag of the same name (see `supabase config pull`'s docs for the reuse/creation rules it follows).

On a fresh checkout, the migration history step runs automatically even without `--with-migration-history`, whenever `supabase/migrations` is missing or a raw directory listing of it turns up no entries at all — the same "existing files" check `migration fetch` itself uses, so a directory holding only a `.gitkeep`/`README.md` already counts as non-empty for this purpose (the listing is unfiltered — any entry at all disqualifies it) and the two commands never disagree about it. There's nothing local to overwrite when the directory is truly empty or missing, and it's what lets the database step run at all: without it, `db pull` would hard-fail comparing an empty local directory against a remote project that already has migration history. Pass `--with-migration-history` to force a re-fetch whenever the directory already has any files in it, including only non-migration ones — unlike the bootstrap case, this DOES overwrite: any local migration file that shares a name with a remote history entry is replaced.

`supabase pull` shows one confirmation before writing anything, covering all four steps. It opens by naming the target (`Pulling from project <ref>`, or with `(branch "<name>")` appended when the target is a branch), then lists the four steps in the order they run: the config step's part is a real diff, computed the same way `config diff`/`config pull` compute theirs (or "No config differences found." when there is nothing to change); the migration-history line only appears when that step will actually run this invocation, and calls out that it overwrites same-named local files when it's running because of `--with-migration-history` rather than the bootstrap case; the database line notes that it also updates the remote migration history table and requires Docker; the functions line describes the download. `--dry-run` prints this exact same disclosure body — not a placeholder or a status-only summary — before exiting without writing or changing anything. `--yes` skips the confirmation and takes its default answer.

`supabase pull` checks THREE locations for uncommitted or untracked changes in git before writing: `supabase/config.toml` (or `config.json`), `supabase/migrations`, and `supabase/functions`. The config check only fires when the config step itself has work to write — a config that's already fully converged with the target never triggers it. The other two fire unconditionally: the database step always attempts to run and has no way to know in advance whether it will find schema drift and write into `supabase/migrations`, and the functions step always runs with no equivalent "nothing to do" signal available without calling the API first — so both are checked every run to avoid silently missing real uncommitted work. Each location's dirty state is tracked separately: the confirmation body and any abort message name exactly which path(s) are actually dirty, e.g. `supabase/config.toml has uncommitted or untracked changes...` for one, or `supabase/config.toml, supabase/migrations, and supabase/functions have uncommitted or untracked changes...` when all three are. `--force` writes even when any of the three is dirty — without it, an interactive run's confirmation defaults to declining instead of proceeding, and every other case (non-interactive, machine output format, or `--yes` on any TTY) aborts outright rather than silently overwriting local edits.

**This command is not purely a local, read-only refresh.** Pulling the database schema also updates that database's own migration history table on the **remote** project — the same behavior `db pull` has always had — not just a local file write. The database step also requires Docker (it runs a shadow Postgres container, and — on the very first pull — a `pg_dump` container) to compute the schema diff. Without Docker running, that one step fails and is reported as such, but the other three steps (config, migration history, functions) still run and complete normally; a project with nothing in its database yet can still successfully pull its config and functions without Docker installed.

If the database is already in sync with the local migrations, that step reports `unchanged` rather than failing — this differs from running `supabase db pull` directly, which treats "nothing to pull" as an error condition.

Storage bucket definitions are not pulled by this command: the Management API doesn't currently return enough detail (file size limits, allowed MIME types, the storage backend path) to populate `storage.buckets` config faithfully.

## Example

```sh
supabase pull
```

Pulls config, database schema, and functions from the linked project, fetching migration history first if `supabase/migrations` is empty.

```sh
supabase pull --project-ref staging
```

Pulls from the `staging` branch of the linked project.

```sh
supabase pull --dry-run
```

Prints the full confirmation body — the target header, the real config diff (or "No config differences found."), the migration-history/database/functions lines (including the Docker mention and, if applicable, the uncommitted-changes warning) — without writing or changing anything.

```sh
supabase pull --remote-label staging
```

Pulls into the `[remotes.staging]` block instead of whatever block the target would otherwise reuse or create.

Machine-readable output is available through `--output-format json|stream-json` — a single object (`schema_version`, `target`, `dry_run`, `confirmed`, `wrote`, `step_order`, `steps`, `counts`) with one entry per step under `steps`, keyed `config`, `migration_history`, `db`, and `functions`, each carrying its own `status` (`changed`, `unchanged`, `skipped`, `planned`, or `failed`), the paths it wrote, and a step-specific `detail` object. The legacy global `-o`/`--output` flag is not supported by this command; use `--output-format json|stream-json` instead.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall