agentleFS
conectlensconectlens/lenserfight/.agents/skills/supabase-schema-reviewer/SKILL.md

supabase-schema-reviewer

Skill18 starsChanged 6 months agoMITView on GitHub

Review Supabase/Postgres schema design, table ownership, normalization, defaults, relationships, and migration coherence. Use for new tables, column design, view design, schema cleanup, and database modeling decisions.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read supabase/migrations/*!

    line 14
  2. Very specific:

    Run 'npx supabase migration up --local' to ensure the created migrations applied successfully

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Supabase Schema Reviewer

Use when

  • adding or changing tables, views, or relationships
  • reviewing naming, ownership, or normalization decisions
  • checking whether migrations form a coherent model

Workflow

  1. Read supabase/migrations/*! Inspect schema intent, ownership model, and relationships.
  2. Flag weak naming, missing constraints, awkward defaults, and modeling debt.
  3. Return exact schema recommendations with migration notes.
  4. Run 'npx supabase migration up --local' to ensure the created migrations applied successfully

Load only when needed

  • Schema review method
  • Schema decision template

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.