run-db-matrix
Runs plugin test matrices locally using both MongoDB and PostgreSQL.
Install
mkdir -p .claude/skills/run-db-matrix && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18160" && unzip -o skill.zip -d .claude/skills/run-db-matrix && rm skill.zipInstalls to .claude/skills/run-db-matrix
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when the user wants to run a single plugin's full Mongo + Postgres test matrix locally. Wraps `pnpm test:matrix <plugin>`.Key capabilities
- →Run a single plugin's Mongo and Postgres test matrix locally
- →Execute integration tests against multiple database engines
- →Verify no leaked processes after tests complete
- →Generate types for a plugin via `pnpm generate <slug>`
- →Migrate a plugin's database via `pnpm migrate <slug>`
How it works
The skill executes `pnpm test:matrix <slug>` and `pnpm test:container <slug>` to run integration tests against Mongo and Postgres, then checks for leaked processes.
Inputs & outputs
When to use run-db-matrix
- →Run plugin test matrix
- →Verify database integration
- →Test production parity
About this skill
Run the DB matrix
- Ask the user which plugin if not obvious from context.
- Run:
pnpm test:matrix <slug>. This runs the plugin once per lane itstest:matrixscript names:DB_MATRIX=mongoandDB_MATRIX=postgreseverywhere, and foranalyticsalsoDB_MATRIX=sqlitetwice, once with the native engine on worker threads (what a WAL file with a 5 s busy timeout gets) and once forced onto the main thread (ANALYTICS_SQLITE_THREAD=main). Mongo runs in-memory; Postgres runs in a realpostgres:16container via testcontainers (Docker required; testcontainers needsDOCKER_HOSTpointed at a Docker socket it cannot find on its own, such as OrbStack's); SQLite runs on a temp libsql file. Coverage is decided in two places: the package'stest:matrixscript decides which spec files run in each lane, and eachdescribeForDbblock'sdbsoption decides which lanes that block joins. Most plugins' scripts name individual spec files (grep -n '"test:matrix"' packages/*/package.json), so a spec missing from that list is silently excluded from Postgres no matter how it is written;analyticsis currently the only plugin whose script runs its wholetests/intdirectory on every lane. A block pinned to one DB likewise runs only where the pin allows. - One lane alone, from the package directory:
DB_MATRIX=sqlite pnpm exec vitest run tests/int. Analytics' config caps a Mongo lane at 3 workers and a Postgres lane at 4 and runs a SQLite lane in forked workers; pass--maxWorkers=3on another plugin's Mongo lane. Run one lane at a time. - For both DBs in containers (max prod parity):
pnpm test:container <slug>. - After tests complete, verify no leaked processes:
pnpm check:processesanddocker ps(testcontainers leave aryukreaper behind for a few seconds). Kill withpnpm clean:processesif needed. - NEVER run
pnpm exec payload generate:*orpnpm exec payload migrate:*directly to "regenerate types" or "set up the DB" as part of debugging; the bin script hangs. Usepnpm generate <slug>/pnpm migrate <slug>which route throughscripts/payload.sh(120s deadline).
When not to use it
- →When the user does not want to run a plugin's full Mongo + Postgres test matrix
- →When the user is not testing locally
- →When the user wants to run `pnpm exec payload generate:*` or `pnpm exec payload migrate:*` directly
Limitations
- →Requires Docker for Postgres container via testcontainers
- →Does not directly run `pnpm exec payload generate:*` or `pnpm exec payload migrate:*`
- →Focuses on a single plugin's test matrix
How it compares
This skill provides a standardized and verified method for running a plugin's full database test matrix locally, including process cleanup, which is more structured than manual command execution.
Compared to similar skills
run-db-matrix side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| run-db-matrix (this skill) | 0 | 4mo | No flags | Intermediate |
| generating-database-seed-data | 10 | 3mo | Review | Intermediate |
| testing-workflow | 16 | 12mo | Review | Intermediate |
| generate-validation-notebook | 0 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
generating-database-seed-data
jeremylongshore
Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
generate-validation-notebook
monte-carlo-data
Generate SQL validation notebooks for dbt changes. Pass a GitHub PR URL or local dbt repo path.
validation
ProfPowell
Validate data with JSON Schema and AJV. Use when validating API requests, form submissions, database inputs, or any data boundaries. Provides deterministic validation with consistent error formats.
cocoindex
cocoindex-io
Comprehensive toolkit for developing with the CocoIndex library. Use when users need to create data transformation pipelines (flows), write custom functions, or operate flows via CLI or API. Covers building ETL workflows for AI data processing, including embedding documents into vector databases, building knowledge graphs, creating search indexes, or processing data streams with incremental updates.
cqrs-implementation
wshobson
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.