agentleFS
Sign inStart free
conectlensconectlens/lenserfight/.agents/skills/database-schema-reviewer/SKILL.md

database-schema-reviewer

Skill18 starsChanged 6 months agoMITView on GitHub

Review PostgreSQL schema design for integrity, performance, and migration safety. Use when modifying supabase/migrations/* or supabase/functions/*.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run database schema review for $ARGUMENTS.

    line 8
  2. Distinctive:

    Read the latest migration files in:

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Run database schema review for $ARGUMENTS.

Purpose
Evaluate database schema quality, integrity, and performance risks.

Primary scope

  • supabase/migrations/*
  • supabase/functions/*
  • supabase/tests/*

Workflow

[ ] 1 Inspect schema definition

Read the latest migration files in:

supabase/migrations/*

[ ] 2 Inspect SQL functions and triggers

Review:

supabase/functions/*

[ ] 3 Evaluate schema integrity

Check:

  • primary keys
  • foreign keys
  • unique constraints
  • nullability rules
  • enum usage

[ ] 4 Evaluate performance risks

Check:

  • missing indexes
  • large relation scans
  • hot tables
  • unbounded joins

[ ] 5 Evaluate migration safety

Look for:

  • destructive schema changes
  • column type rewrites
  • large table locks
  • incompatible constraints

Load references only when needed

  • Review process: Schema review method
  • Integrity rules: Database constraints and relationship checks
  • Performance rules: Indexing and query optimization guidance
  • Security rules: RLS policies and database security checks

Output

Report:

  • schema risks
  • missing constraints
  • index recommendations
  • migration safety issues
  • suggested improvements

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.

Check your setup, free