nginx-c-module-debug

nginx C module debugging guidelines based on the official nginx development guide. This skill should be used when debugging nginx C module crashes, memory bugs, request flow issues, or production problems. Triggers on tasks involving segfault analysis, coredump debugging, GDB inspection, memory leak detection, request phase tracing, AddressSanitizer setup, or nginx module troubleshooting.

跳到安装

仓库: pproenca/dot-skills
最近来源活动: 2026年5月27日 09:50
检测到的 SKILL.md 语言: 英语
星标: 194
分支: 17

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

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

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/pproenca/dot-skills --skill nginx-c-module-debug

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

49 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

drizzle-nextjs-postgres

Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.

2026-07-24

relational-data-modeling

Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.

2026-07-23

relational-database-design

Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.

2026-07-23

查看这个仓库的全部 Skills

name	nginx-c-module-debug
description	nginx C module debugging guidelines based on the official nginx development guide. This skill should be used when debugging nginx C module crashes, memory bugs, request flow issues, or production problems. Triggers on tasks involving segfault analysis, coredump debugging, GDB inspection, memory leak detection, request phase tracing, AddressSanitizer setup, or nginx module troubleshooting.

nginx.org C Module Debugging Best Practices

Comprehensive debugging guide for nginx C modules, derived from the official nginx development documentation and production debugging experience. Contains 45 rules across 8 categories, prioritized by impact to guide systematic diagnosis of crashes, memory bugs, and behavioral issues in nginx modules.

Companion skills: This skill complements nginx-c-modules (correctness) and nginx-c-module-perf-reliability (performance). This skill covers debugging and diagnosis.

When to Apply

Reference these guidelines when:

Diagnosing nginx worker crashes (segfaults, SIGABRT, SIGSEGV)
Finding memory bugs (use-after-free, leaks, pool corruption, buffer overruns)
Setting up GDB and core dump analysis for nginx
Tracing request flow through phases, subrequests, and filter chains
Instrumenting nginx modules with debug logging and dynamic tracing tools

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Crash Diagnosis & Signals	CRITICAL	`crash-`
2	Memory Bug Detection	CRITICAL	`memdbg-`

File	Description
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

nginx-c-module-debug

安装方式

检查来源文件

nginx.org C Module Debugging Best Practices

When to Apply

Rule Categories by Priority

nginx.org C Module Debugging Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Crash Diagnosis & Signals (CRITICAL)

2. Memory Bug Detection (CRITICAL)

3. GDB & Core Dump Analysis (HIGH)

4. Request Flow Tracing (HIGH)

5. Debug Logging Patterns (MEDIUM-HIGH)

6. State & Lifecycle Debugging (MEDIUM)

7. Dynamic Tracing Tools (MEDIUM)

8. Build & Sanitizer Configuration (LOW-MEDIUM)

How to Use

Reference Files

nginx-c-module-debug

来源信息

安装方式

检查来源文件

同仓库更多 Skills

nginx.org C Module Debugging Best Practices

When to Apply

Rule Categories by Priority

nginx.org C Module Debugging Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Crash Diagnosis & Signals (CRITICAL)

2. Memory Bug Detection (CRITICAL)

3. GDB & Core Dump Analysis (HIGH)

4. Request Flow Tracing (HIGH)

5. Debug Logging Patterns (MEDIUM-HIGH)

6. State & Lifecycle Debugging (MEDIUM)

7. Dynamic Tracing Tools (MEDIUM)

8. Build & Sanitizer Configuration (LOW-MEDIUM)

How to Use

Reference Files

同仓库更多 Skills