一键在 Manus 中运行任何 Skill

postgresq

星标1

分支0

更新时间2026年5月26日 12:00

Research the PostgreSQL community via the agora MCP server (https://pg.ddx.io/mcp/). Use when investigating PostgreSQL internals or extension development, reviewing or writing patches, understanding historical design decisions, finding related prior art, or tracing a feature through 76k+ pgsql-hackers messages and the upstream/master git history.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

gburd

gburd/nix-config

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

PostgreSQL Community Research

Use the postgresq MCP server (https://pg.ddx.io/mcp/) to research PostgreSQL community discussions, patches, and development history.

Capabilities

Search 76K+ mailing list messages across all PostgreSQL lists
Find related patches and review discussions
Trace feature development history through commit archaeology
Understand community coding conventions and review standards

When to Use

Investigating PostgreSQL internals or extension development
Reviewing or writing patches for PostgreSQL
Understanding historical design decisions
Finding related prior art for database features

References

See the references/ directory for detailed specs on:

code-review.md — How to review PostgreSQL patches
community-context.md — Understanding community norms
research-hackers.md — Searching pgsql-hackers effectively

同仓库更多 Skills

同仓库

aws-benchmark

gburd/nix-config

Run performance benchmarks on AWS EC2 (bare-metal or regular instances) with a reproducible launch → tune → measure → terminate workflow. Use for ANY AWS benchmarking — CPU/memory/IO/database/application, NUMA-related or not: choosing + launching an instance, one-time key-pair/security-group setup, OS kernel tuning (hugepages, governor, THP, NUMA balancing), EBS provisioning, A/B methodology, collecting results, and (critically) terminating the instance when done so it stops costing money. Triggers on: "benchmark on AWS/EC2", "bare-metal EC2", "launch an instance to test", "A/B benchmark", "clock sweep / NUMA benchmark", "pgbench/HammerDB on EC2". For the PostgreSQL-buffer-manager clock-sweep specifics, this pairs with the pg-numa-benchmark skill (which uses this one for the AWS substrate).

2026-07-081

pg-numa-benchmark

gburd/nix-config

Run PostgreSQL clock sweep benchmarks on bare-metal EC2 instances. Covers AWS setup, instance launch (r8i.metal-96xl / m6i.metal), OS tuning, PG build (stock + patched), pgbench A/B testing, HammerDB TPC-C, and result collection. Use when benchmarking PostgreSQL buffer manager changes on NUMA hardware. The generic AWS benchmarking substrate (launch/tune/A-B/terminate) is in the aws-benchmark skill; this layers the PostgreSQL specifics on top.

2026-07-081

nix-agent-configs

gburd/nix-config

Hard-won lessons for working on the Nix-managed AI agent configs in modules/home-manager/ai/ (the Bedrock-backed agents pi, claude, maki, hermes, codex, plus kiro-cli, and the LiteLLM proxy). Use this skill ONLY when editing files under modules/home-manager/ai/ or debugging agent auth/telemetry/model routing. Covers: telemetry-off enforcement, thinking-effort ceilings, the two Bedrock auth paths (bearer vs SigV4), model-reachability verification, patching pipx/venv tools, and the CI expectations for this repo. Triggers on: editing modules/home-manager/ai, "LiteLLM proxy", "Bedrock auth", "agent telemetry", "thinking effort", "kiro-cli config".

2026-07-031

release-tagging

gburd/nix-config

Date-based release tagging conventions for this maintainer's personal repos (nix-config and other single-author repos). Use this skill ONLY when actually cutting a release or creating/pushing a git tag — the commit→push→tag→push-tag flow, the vYYYY.MM.DD[.N] format, and the deliberate maintainer exceptions to the "never push to main / never force-push" rules. Triggers on: "tag a release", "cut a release", "ship this", "create a tag", "vYYYY.MM.DD".

2026-07-031

subagent-teams

gburd/nix-config

How to run coordinated sub-agent teams (worker → reviewer → re-reviewer) and the Bedrock model-dispatch rules for sub-agents. Use this skill ONLY when spawning/dispatching sub-agents (e.g. Pi's Agent tool, parallel task fan-out) or debugging a sub-agent that dies instantly. Triggers on: "sub-agent", "subagent", "dispatch agents", "parallel agents", "Agent tool", "sub-agent finished in <2s / 0 tool uses".

2026-07-031

coccinelle

gburd/nix-config

Run semantic patches on C/C++ via spatch. Use for AST-level refactoring, finding API usage patterns, enforcing coding standards structurally, migrating deprecated APIs, and finding null-deref / resource-leak patterns across large codebases. Pairs with the Pi `coccinelle` extension's pre-defined patterns (null-checks, error-handling, memory-leaks, resource-leaks, dead-code, simplify-conditionals, const-correctness).

2026-05-261

name	postgresq
description	Research the PostgreSQL community via the agora MCP server (https://pg.ddx.io/mcp/). Use when investigating PostgreSQL internals or extension development, reviewing or writing patches, understanding historical design decisions, finding related prior art, or tracing a feature through 76k+ pgsql-hackers messages and the upstream/master git history.

PostgreSQL Community Research

Use the postgresq MCP server (https://pg.ddx.io/mcp/) to research PostgreSQL community discussions, patches, and development history.

Capabilities

Search 76K+ mailing list messages across all PostgreSQL lists
Find related patches and review discussions
Trace feature development history through commit archaeology
Understand community coding conventions and review standards

When to Use

Investigating PostgreSQL internals or extension development
Reviewing or writing patches for PostgreSQL
Understanding historical design decisions
Finding related prior art for database features

References

See the references/ directory for detailed specs on:

code-review.md — How to review PostgreSQL patches
community-context.md — Understanding community norms
research-hackers.md — Searching pgsql-hackers effectively