common-mistakes

Enforce pgdbm rules for pools, migrations, templates, and schema management.

Updated Jul 28, 2025
One-click install
npx skills add https://github.com/juanre/pgdbm --skill common-mistakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: common-mistakes
Source: https://github.com/juanre/pgdbm/tree/main/skills/common-mistakes
Command: npx skills add https://github.com/juanre/pgdbm --skill common-mistakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid common pgdbm implementation mistakes by codifying hard-won rules, red flags, and debugging guidance before coding patterns.

Core Features & Use Cases

  • Iron Rules: enforce single database pools, proper template usage, unique module names, and never switch schema at runtime.
  • Red Flags: identify pitfalls like hardcoded schema/table names, silent cleanup issues, and shared pools across services.
  • Symptom-Based Debugging: provides practical checks and debugging steps to diagnose pool, migration, and schema issues in real projects.

Quick Start

Review the common-mistakes guide and apply its rules to your pgdbm integration tasks before coding.

Frequently Asked Questions about common-mistakes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the most common pgdbm mistakes to avoid?

Common pgdbm mistakes include creating multiple pools per database, using hardcoded schema and table names instead of {{tables.*}}, omitting module_name, and switching schema at runtime. This Skill codifies these hard-won rules and red flags to prevent them before coding begins.

How do I set up database connection pools correctly in pgdbm?

Enforce one pool per database as an iron rule. Specify a unique module_name for each pool, avoid sharing pools across services, and never hardcode schema or table references. Apply these checks before implementing pool configuration.

Why are my pgdbm migrations or schema changes failing silently?

Silent failures often stem from shared pools across services, incorrect template syntax (missing {{tables.*}}), or schema switching at runtime. This Skill provides symptom-based debugging steps to diagnose pool, migration, and schema issues in real projects.

Do I need to use template syntax in pgdbm configurations?

Yes. Always use {{tables.*}} in pgdbm templates instead of hardcoding table names. This syntax is mandatory for proper schema management and prevents common pitfalls in both single- and multi-service setups.

What's the difference between single-service and multi-service pgdbm setups?

Both require the same iron rules: one pool per database, proper template usage, unique module names, and no runtime schema switching. This Skill applies debugging guidance and red flags across both architectures.