PostgreSQL专家最佳实践与代码审查指南 - 生产级数据库优化规则

postgresql-expert-best-practices-code-review by wispbit-ai/skills

238 周安装量

6 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/wispbit-ai/skills --skill postgresql-expert-best-practices-code-review

数据库代码规范性能优化

🇨🇳中文介绍

PostgreSQL 专家最佳实践

简洁、实用、观点鲜明。仅包含编写生产级 PostgreSQL 查询所需的关键要点。

适用场景

在以下情况时参考本指南：

编写数据库迁移或模式变更
创建或修改 PostgreSQL 表和列
添加索引、约束或外键
审查数据库模式以排查性能问题
重构现有数据库结构
优化查询性能或数据库设计

按优先级划分的规则类别

优先级	类别	影响	前缀
1	索引管理	关键-高	`only-concurrent-indexes`, `add-index-for-foreign-key`
2	约束安全	高	`unique-constraint`, ,

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

PostgreSQL Expert Best Practices

Simple, pragmatic, opinionated. Only what matters for writing production-grade PostgreSQL queries.

When to Apply

Reference these guidelines when:

Writing database migrations or schema changes
Creating or modifying PostgreSQL tables and columns
Adding indexes, constraints, or foreign keys
Reviewing database schema for performance issues
Refactoring existing database structures
Optimizing query performance or database design

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Index Management	CRITICAL-HIGH	`only-concurrent-indexes`, `add-index-for-foreign-key`
2	Constraint Safety	HIGH	`unique-constraint`, `split-foreign-key`, `set-column-not-null`
3	Schema Design	MEDIUM	`only-jsonb`, `always-include-columns`, `limit-non-unique-index`
4	Naming Standards	LOW	`index-naming-standards`, `column-naming-standards`

Quick Reference

only-concurrent-indexes - Always use CONCURRENTLY to prevent blocking writes during index creation
add-index-for-foreign-key - Create indexes for foreign keys to improve query performance
unique-constraint - Split unique constraint creation into concurrent index + constraint steps
split-foreign-key - Add foreign keys without validation first, then validate separately
set-column-not-null - Use check constraints before setting NOT NULL to avoid table locks
only-jsonb - Use JSONB instead of JSON for better performance and indexing capabilities
always-include-columns - Include id, created_at, and updated_at in all tables for auditability
limit-non-unique-index - Limit non-unique indexes to maximum three columns for efficiency

How to Use

Read individual rule files for detailed explanations and code examples:

rules/only-concurrent-indexes.md
rules/add-index-for-foreign-key.md
rules/unique-constraint.md
rules/split-foreign-key.md
rules/set-column-not-null.md
rules/only-jsonb.md
rules/always-include-columns.md
rules/limit-non-unique-index.md
rules/index-naming-standards.md
rules/column-naming-standards.md

Each rule file contains:

Brief explanation of why it matters
Impact level and description
Incorrect migration example with explanation
Correct migration example with best practices
Additional context and references

Weekly Installs

219

Repository

wispbit-ai/skills

GitHub Stars

First Seen

Feb 10, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

cursor203

opencode113

codex107

github-copilot106

gemini-cli102

claude-code87