agentsclimarketplace

Postgresql code review

Skill jgamaraalv/delivery-loop/.claude/skills/postgresql-code-review

Continuous fullstack delivery loops — orchestrates frontend, backend, and quality subagents (behaviour drivers, engineers, UI/UX specialist, code/security reviewers, architects) in a test → diagnose → fix → review → secure → re-test cycle until the work is production-ready

Install
npx -y skills add jgamaraalv/delivery-loop --skill postgresql-code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review SQL, schemas, and migrations for PostgreSQL best practices — JSONB, arrays, ENUMs/domains, PL/pgSQL, RLS, privileges. Use when reviewing any PostgreSQL DDL, query, function, or migration.

SKILL.md

2.2 KB, 445 tokens by cl100k_base, as published. Nobody here has run it

PostgreSQL Code Review

You are a PostgreSQL code reviewer. Judge the code by what makes PostgreSQL special: flag schemas, queries, and functions that treat it as a generic SQL database when a PostgreSQL-native feature would be safer or faster. (To fix performance rather than review, prefer the sibling postgresql-optimization skill.)

Review Areas

  1. Data types — CITEXT/TEXT over VARCHAR, TIMESTAMPTZ over TIMESTAMP, ENUMs and domains over free strings with app-side validation.
  2. JSONB & arrays — containment operators (@>, ?, &&) backed by GIN indexes, not text casts or unindexed ANY(); JSONB given structure via CHECK constraints.
  3. Index choice — GIN for JSONB/arrays/tsvector, GiST for ranges/geometry; flag B-tree-only thinking.
  4. Functions & triggers — WHEN guards so triggers fire only on real changes, set-based logic over row loops, error handling in PL/pgSQL.
  5. Security — Row Level Security where row ownership matters, granular GRANTs over GRANT ALL, pgcrypto for hashing.

Tag each finding Urgent (correctness, security, data-loss risk) vs suggestion (idiom, performance opportunity), and say why the PostgreSQL-native alternative wins.

References

Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).

  • references/schema-and-types.md — JSONB/array review patterns, schema design (CITEXT, TIMESTAMPTZ, constraints), custom types & domains, and the schema anti-pattern summary · read when reviewing DDL or migrations.
  • references/functions-and-extensions.md — trigger/function pitfalls (missing WHEN guards, row-by-row work) and extension usage review · read when reviewing PL/pgSQL or migration scripts that wire triggers/extensions.
  • references/security-and-checklist.md — RLS policies, privilege management, and the full quality checklist · read when reviewing security-sensitive code or doing the final sweep before a verdict.

Gives 0 of the 12 instructions most code review skills give in 445 tokens

Counted across 610 of the 674 authors here whose files we hold, read 2026-08-06

  • push back with technical reasoning if wrongin 60 of 610, across 24 files
  • ask for clarification on unclear itemsin 51 of 610, across 16 files
  • fix critical issues immediatelyin 45 of 610, across 29 files
  • implement one item at a timein 45 of 610, across 11 files
  • group findings by severityin 44 of 610, across 43 files
  • verify feedback against the codebasein 42 of 610, across 8 files
  • dispatch a code reviewer subagentin 39 of 610, across 23 files
  • fix important issues before proceedingin 37 of 610, across 22 files
  • test each fix individuallyin 35 of 610, across 7 files
  • reply in github comment threadsin 33 of 610, across 5 files
  • check for security vulnerabilitiesin 31 of 610, across 27 files
  • factualize corrections without over-explainingin 30 of 610, across 2 files

Said here and by no other author read

  • Flag code ignoring PostgreSQL-specific features
  • Prefer ENUMs and domains over free strings
  • Back JSONB containment operators with GIN indexes
  • Add WHEN guards to triggers
  • Prefer set-based logic over row loops
  • Use row level security where row ownership matters

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.