How do I install the Faasjs Pg skill?

Run npx skillmds@latest add faasjs/faasjs-pg in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Faasjs Pg safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Faasjs Pg?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Faasjs Pg free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Faasjs Pg?

faasjs (@faasjs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Faasjs Pg by faasjs — Agent Skill

Name: Faasjs Pg
Rating: 4.2 (5 reviews)
Author: faasjs

Faasjs Pg

Use when working with @faasjs/pg or PostgreSQL in FaasJS: Tables declaration merging, QueryBuilder, select aliases, parameterized sql expressions, raw SQL, numeric/decimal/bigint boundaries, transaction isolation and read-only modes, row locks, concurrency, migrations, SchemaBuilder, TableBuilder, faasjs-pg CLI, PgVitestPlugin, shared migration snapshots, per-file test database isolation, and database type tests.

faasjs f8a5157 7 files · 33.3 KB Updated Sep 10, 2026

File contents

FaasJS PostgreSQL

Default Workflow

Keep table declarations, migrations, queries, and tests aligned.
Prefer typed QueryBuilder clauses before raw SQL.
Parameterize raw SQL values and keep trusted boundaries explicit.
Keep migrations deterministic, lexically sortable, and reversible where possible.
Pair runtime database assertions with type assertions when query inference is part of the behavior.
Use explicit transactions and concurrency tests when atomicity or row locking matters.

Load These References

Declaration merging on Tables and concrete row shapes: references/guidelines/pg-table-types.md.
QueryBuilder, aliases, raw SQL, update expressions, returning, and edge semantics: references/guidelines/pg-query-builder.md.
Transaction modes, transaction client lifetime, row locks, retry ownership, and concurrency tests: references/guidelines/pg-transactions-and-locking.md.
Exact numeric, decimal, and bigint values across TypeScript and API boundaries: references/guidelines/pg-numeric-boundaries.md.
Timestamped migrations, SchemaBuilder, TableBuilder, and schema execution: references/guidelines/pg-schema-and-migrations.md.
PgVitestPlugin(), shared migration snapshots, per-file database isolation, DATABASE_URL, and expectTypeOf(...): references/guidelines/pg-testing.md.

Gotchas

Treat Tables declarations as the source of truth for query inference.
Use raw SQL deliberately; move repeated raw SQL back toward shared helpers or builder clauses.
Keep write queries and transactions guarded by caller scope and expected failure handling; never let a transaction client escape its callback.
Let PgVitestPlugin() own the lazy global setup: it migrates one run-scoped snapshot and gives every database-using test file an isolated clone.
When a transaction also calls enqueueJob, load FaasJS API And Jobs and test rollback of both business data and the job row.
DATABASE_URL is required for migration and PG integration test commands.

Validation

Run npx faasjs-pg migrate when schema changes need migration verification and DATABASE_URL is available.
Run focused PG tests with vp test <pattern>.
Include expectTypeOf(...) when changing type-sensitive query behavior.
Use overlapping real transactions for lock or concurrency behavior; generated SQL assertions alone are insufficient.

---name: faasjs-pgdescription: Use when working with @faasjs/pg or PostgreSQL in FaasJS: Tables declaration merging, QueryBuilder, select aliases, parameterized sql expressions, raw SQL, numeric/decimal/bigint boundaries, transaction isolation and read-only modes, row locks, concurrency, migrations, SchemaBuilder, TableBuilder, faasjs-pg CLI, PgVitestPlugin, shared migration snapshots, per-file test database isolation, and database type tests.---# FaasJS PostgreSQL## Default Workflow1. Keep table declarations, migrations, queries, and tests aligned.2. Prefer typed `QueryBuilder` clauses before raw SQL.3. Parameterize raw SQL values and keep trusted boundaries explicit.4. Keep migrations deterministic, lexically sortable, and reversible where possible.5. Pair runtime database assertions with type assertions when query inference is part of the behavior.6. Use explicit transactions and concurrency tests when atomicity or row locking matters.## Load These References- Declaration merging on `Tables` and concrete row shapes: `references/guidelines/pg-table-types.md`.- `QueryBuilder`, aliases, raw SQL, update expressions, `returning`, and edge semantics: `references/guidelines/pg-query-builder.md`.- Transaction modes, transaction client lifetime, row locks, retry ownership, and concurrency tests: `references/guidelines/pg-transactions-and-locking.md`.- Exact `numeric`, `decimal`, and `bigint` values across TypeScript and API boundaries: `references/guidelines/pg-numeric-boundaries.md`.- Timestamped migrations, `SchemaBuilder`, `TableBuilder`, and schema execution: `references/guidelines/pg-schema-and-migrations.md`.- `PgVitestPlugin()`, shared migration snapshots, per-file database isolation, `DATABASE_URL`, and `expectTypeOf(...)`: `references/guidelines/pg-testing.md`.## Gotchas- Treat `Tables` declarations as the source of truth for query inference.- Use raw SQL deliberately; move repeated raw SQL back toward shared helpers or builder clauses.- Keep write queries and transactions guarded by caller scope and expected failure handling; never let a transaction client escape its callback.- Let `PgVitestPlugin()` own the lazy global setup: it migrates one run-scoped snapshot and gives every database-using test file an isolated clone.- When a transaction also calls `enqueueJob`, load FaasJS API And Jobs and test rollback of both business data and the job row.- `DATABASE_URL` is required for migration and PG integration test commands.## Validation- Run `npx faasjs-pg migrate` when schema changes need migration verification and `DATABASE_URL` is available.- Run focused PG tests with `vp test <pattern>`.- Include `expectTypeOf(...)` when changing type-sensitive query behavior.- Use overlapping real transactions for lock or concurrency behavior; generated SQL assertions alone are insufficient.

Frequently asked questions