メニュー
Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44).
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/CleanExpo/Unite-Group --skill supabase-db-branchコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
The authoritative environment-variable registry for the Unite-Group Nexus. Use whenever adding, reading, renaming, or debugging an env var or secret — new integration config, a `process.env.X` read, an auth/OAuth wiring, a cron secret, a "which variable holds this" question, or a "works locally but not in prod" symptom. Also use before pinning any variable name in code, and when reconciling the two credential planes (Vercel prod vs the local hermes fleet). Prevents the `APIFY_API_KEY` vs `APIFY_API_TOKEN` class of drift.
Verify production Supabase schema before shipping code that touches it. Use BEFORE writing or reviewing ANY code that reads or writes a Supabase table in the Nexus — new queries, inserts, updates, CHECK-constrained values, RLS-dependent reads, cron data access — even one-line changes and even when the table "obviously" exists. Also use immediately when a query fails with "column does not exist", when inserts appear to succeed but produce no rows, or when generated TypeScript types disagree with runtime behaviour.
Brand context for the ITR Button tax app (ato-ai.app) — write on-voice, factually-grounded, compliance-safe content. Fires when producing content for this AI tax-return-intake tool (org slug `ato` in credential-triage event routing). Loads brand, voice, key entities, and the CRITICAL guardrail that separates it from the government ATO and keeps every claim inside TASA s90-5 (tool, not tax-agent service).
SKILL.md を表示中
| name | supabase-db-branch |
| description | Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44). |
Every schema change/migration to the Nexus Supabase instance must be validated on a Supabase database branch before promotion to prod. This skill defines the standard process for creating, testing, and promoting schema changes via branches.
Create a branch off prod
schema-change-<description>-<timestamp>persistent: false by default (reaped after inactivity)persistent: trueApply the migration(s) to the branch
supabase db pushsupabase migration list --localRun supabase-schema-gate checks against the branch
Verify idempotency
IF NOT EXISTS guards or DO $$ blocksEvidence and promotion
IF NOT EXISTS idempotency guards against partial application; fix the error on the branch, re-pushpersistent: false (automatically reaped after inactivity)persistent: true for CI backends (e.g., e2e-gate)