// 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.
Verdict PR review comments pragmatically - address valid ones, dismiss over-engineered or incorrect ones, and respond to each. Use this skill when handling PR review feedback, code review comments, or when asked to address reviewer suggestions.
Fix a bug from a GitHub issue using TDD. Analyzes the issue, creates a reproducing test case, implements the fix, verifies it, and creates a PR. Use this skill whenever working on a GitHub issue, bug report, or regression — even if the user just provides an issue number or URL.
Consult PostgreSQL's pg_dump implementation for guidance on system catalog queries and schema extraction when implementing pgschema features. Use this skill when adding new schema object support, debugging inspector.go queries, understanding how PostgreSQL represents objects internally, or handling version-specific features across PostgreSQL 14-18.
Consult PostgreSQL's parser and grammar (gram.y) to understand SQL syntax, DDL statement structure, and parsing rules when implementing pgschema features. Use this skill when generating DDL in internal/diff/*.go, validating SQL syntax, understanding keyword precedence, or learning how PostgreSQL handles specific constructs like triggers, indexes, generated columns, or constraint triggers.
Connect to live PostgreSQL database to validate schema assumptions, compare pg_dump vs pgschema output, and query system catalogs interactively. Use this skill whenever you need to test queries against a real database, verify how PostgreSQL stores or formats objects, debug introspection issues, or check version-specific behavior (PostgreSQL 14-18).
| name | run_tests |
| description | 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. |
Run pgschema tests for validating implementation changes.
| 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 |
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/
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.
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.
mkdir -p testdata/diff/<category>/<test_name>old.sql (starting state) and new.sql (desired state)PGSCHEMA_TEST_FILTER="<category>/<test_name>" go test -v ./cmd -run TestPlanAndApply --generatediff.sql and plan files--generate to verifyFor dump tests, create testdata/dump/<name>/ with manifest.json, raw.sql, pgdump.sql, pgschema.sql and register in cmd/dump/dump_integration_test.go.
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
go test -v ./... (or scoped to affected areas if full suite times out)| Variable | Purpose | Example |
|---|---|---|
PGSCHEMA_TEST_FILTER | Run specific test cases | "create_trigger/" |
PGSCHEMA_POSTGRES_VERSION | Test specific PG version | 14, 17 |