pgplexpgplex/pgschema/.claude/skills/run_tests/SKILL.md

run_tests

Skill1.1k starsChanged 9 months agoApache-2.0View on GitHub

Run pgschema automated tests (go test) to validate diff logic, plan generation, and dump functionality using test fixtures. Use this skill whenever you need to run tests, debug test failures, add new test cases, regenerate expected outputs, or validate changes across PostgreSQL versions 14-18.

2 other projects use a version of this.

Aug 4, 2026feat: harden sql contract boundaries — ONREZA/sqlx-js1 reaction
Nov 12, 2026pgschema: 1.13.4 -> 1.14.1 — NixOS/nixpkgs0 reactions · 1 comment
Nov 8, 2026ci(deps): Update release supply chain — yuniruyuni/FighterNotes0 reactions · 1 comment
Nov 8, 2026agent-skills.github.pgplex.pgschema: 1.14.0 → 1.14.1 — sudosubin/agents.nix0 reactions
Nov 6, 2026agent-skills.github.pgplex.pgschema: 1.13.4 → 1.14.0 — sudosubin/agents.nix0 reactions

17 more on GitHub

Oct 31, 2026pgschema: 1.13.3 -> 1.13.4 — NixOS/nixpkgs0 reactions · 3 comments
Oct 30, 2026ci(deps): Update release supply chain — yuniruyuni/FighterNotes0 reactions · 2 comments
Oct 27, 2026agent-skills.github.pgplex.pgschema: 1.13.3 → 1.13.4 — sudosubin/agents.nix0 reactions
Oct 19, 2026pgschema: 1.13.1 -> 1.13.3 — NixOS/nixpkgs0 reactions · 4 comments
Oct 15, 2026agent-skills.github.pgplex.pgschema: 1.13.2 → 1.13.3 — sudosubin/agents.nix0 reactions
Oct 15, 2026agent-skills.github.pgplex.pgschema: 1.13.1 → 1.13.2 — sudosubin/agents.nix0 reactions
Oct 11, 2026chore(deps): update release supply chain — yuniruyuni/FighterNotes0 reactions · 1 comment
Oct 1, 2026agent-skills.github.pgplex.pgschema: init at 1.13.1 — sudosubin/agents.nix0 reactions
Sep 27, 2026pgschema: 1.13.0 -> 1.13.1 — NixOS/nixpkgs0 reactions · 4 comments
Sep 17, 2026pgschema: 1.12.5 -> 1.13.0 — NixOS/nixpkgs0 reactions · 5 comments
Sep 6, 2026pgschema: 1.12.4 -> 1.12.5 — NixOS/nixpkgs0 reactions · 4 comments
Aug 27, 2026pgschema: 1.12.3 -> 1.12.4 — NixOS/nixpkgs0 reactions · 1 comment
Jun 15, 2026sha256 is inconsistent with the one on github release — pgplex/homebrew-pgschema0 reactions
Apr 22, 2026pg-delta: add enum-arg function privilege parity coverage (pgschema #366) — supabase/pg-toolbelt0 reactions · 1 comment
Apr 22, 2026pg-delta: add parity coverage for DEFERRABLE UNIQUE constraints (pgschema #404) — supabase/pg-toolbelt0 reactions · 2 comments
Mar 5, 2026Daily scan, git submodules, GitHub Models API, Copilot instruction docs — avallete/delta-schema-compare0 reactions
Mar 3, 2026Joergs TODO list — numtide/llm-agents.nix0 reactions

Other versions2 projects use a version of this.
Word for word · 1
pgschema/pgschema★ 1.1k100% same
Edited · 0
None found.
Wrote their own version · 1
androidx/androidx★ 6.1ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fix_bugSkill
- pg_dumpSkill
- postgres_syntaxSkill
- review_commentsSkill
- validate_dbSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Run pgschema tests for validating implementation changes.
line 8
Very specific:
Use PGSCHEMA_TEST_FILTER to scope to specific cases:
line 20
Distinctive:
When implementation intentionally changes generated DDL:
line 34
Very specific:
Create old.sql (starting state) and new.sql (desired state)
line 54
Very specific:
Run without --generate to verify
line 57

≈ “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 Tests

Run pgschema tests for validating implementation changes.

Test Types

Type	Command	Speed	What it tests
Diff	`go test -v ./internal/diff -run TestDiffFromFiles`	~2s	Schema comparison logic (no DB)
Plan/Apply	`go test -v ./cmd -run TestPlanAndApply`	~30-60s	Full workflow with embedded PostgreSQL
Dump	`go test -v ./cmd/dump -run TestDumpCommand`	~10-20s	Schema extraction from test databases

Filtering Tests

Use PGSCHEMA_TEST_FILTER to scope to specific cases:

# Specific test case
PGSCHEMA_TEST_FILTER="create_trigger/add_trigger_when_distinct" go test -v ./internal/diff -run TestDiffFromFiles

# All tests in a category
PGSCHEMA_TEST_FILTER="create_trigger/" go test -v ./cmd -run TestPlanAndApply

Categories (in testdata/diff/): comment/, create_domain/, create_function/, create_index/, create_materialized_view/, create_policy/, create_procedure/, create_sequence/, create_table/, create_trigger/, create_type/, create_view/, default_privilege/, privilege/, dependency/, online/, migrate/

Regenerating Expected Output

When implementation intentionally changes generated DDL:

PGSCHEMA_TEST_FILTER="category/test_name" go test -v ./cmd -run TestPlanAndApply --generate

This overwrites diff.sql, plan.json, plan.sql, plan.txt. Always review with git diff afterward and re-run without --generate to confirm.

Testing Across PostgreSQL Versions

PGSCHEMA_POSTGRES_VERSION=14 go test -v ./cmd/dump -run TestDumpCommand_Employee
PGSCHEMA_POSTGRES_VERSION=17 PGSCHEMA_TEST_FILTER="create_trigger/" go test -v ./cmd -run TestPlanAndApply

Supported: 14, 15, 16, 17, 18.

Adding a New Test Case

Create directory: mkdir -p testdata/diff/<category>/<test_name>
Create old.sql (starting state) and new.sql (desired state)
Generate expected files: PGSCHEMA_TEST_FILTER="<category>/<test_name>" go test -v ./cmd -run TestPlanAndApply --generate
Review generated diff.sql and plan files
Run without --generate to verify

For dump tests, create testdata/dump/<name>/ with manifest.json, raw.sql, pgdump.sql, pgschema.sql and register in cmd/dump/dump_integration_test.go.

Test Data Structure

testdata/diff/<category>/<test_name>/
├── old.sql       # Starting schema
├── new.sql       # Desired schema
├── diff.sql      # Expected migration DDL
├── plan.json     # Plan in JSON
├── plan.sql      # Plan as SQL
└── plan.txt      # Plan as text

Recommended Testing Order

Fast iteration: diff tests first (no DB startup)
Full validation: integration tests for the same category
Before commit: go test -v ./... (or scoped to affected areas if full suite times out)

Environment Variables

Variable	Purpose	Example
`PGSCHEMA_TEST_FILTER`	Run specific test cases	`"create_trigger/"`
`PGSCHEMA_POSTGRES_VERSION`	Test specific PG version	`14`, `17`

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