find-postgres-bug

Find latent bugs in a local PostgreSQL source tree (REL_xx_STABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core dumps), fuzz it (sqlsmith) until the backend crashes, triage the core into a minimal reproducer (MRE), git-bisect the introducing commit, and render a community-style pgsql-bugs markdown report. The instance never auto-shuts-down. Use when the user says "find a bug in postgres", "fuzz postgres", "hunt for a crash", "test a recent commit", "write a repro", "bisect this crash", "把 PG 跑起来找 bug", "fuzz 一下 postgres", "看看这个 commit 会不会出问题", etc. Triggers whenever the user points at a PG source dir and wants to hunt bugs.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, highly actionable skill body with a well-sequenced validated workflow and excellent progressive disclosure; the only nit is minor redundancy between the TL;DR decision tree, the 'does not do' section, and the workflow steps.

Suggestions

Trim the 'Decision tree (TL;DR)' or explicitly label it as a recap so it doesn't read as duplicated workflow content, recovering conciseness without losing the at-a-glance map.

Collapse 'What this skill does not do' into the existing 'Three hard rules' block to avoid restating the no-patch / no-auto-stop commitments twice.

Consider moving the full 'Output format' required-sections list into the bug_report_template reference and keeping only a one-line pointer inline.

Dimension	Reasoning	Score
Conciseness	Lean and purposeful with no basic-concept padding, but the 'Decision tree (TL;DR)' largely reiterates the Step 0–6 workflow and 'What this skill does not do' partly restates the three hard rules — minor redundancy an otherwise tight body could trim.	4 / 5
Actionability	Fully executable throughout: Quick start gives copy-paste commands and each workflow step cites an exact script invocation with arguments (e.g. './scripts/fuzz_sqlsmith.sh 3600 postgres', './scripts/bisect_run.sh repro/mybug.sql REL_17_STABLE HEAD'), backed by a complete script reference table.	5 / 5
Workflow Clarity	Steps 0–8 are clearly sequenced, each closing with an explicit 'Success:' validation checkpoint, plus a pre-flight gate and feedback loops (dirty tree → stop and ask; 'Cache poison: none' → re-enable); destructive/batch operations are validated, so no cap applies.	5 / 5
Progressive Disclosure	Clear overview body pointing to one-level-deep, self-contained references (9 files), 12 scripts, and a template — all referenced paths verified present — with a descriptive reference index making navigation easy.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: specific, comprehensive, third-person, with concrete what/when framing and rich natural trigger terms in two languages. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with implementation specifics — 'build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core dumps)', 'fuzz it (sqlsmith)', 'triage the core into a minimal reproducer (MRE)', 'git-bisect the introducing commit', 'render a community-style pgsql-bugs markdown report' — giving comprehensive coverage of the pipeline.	5 / 5
Completeness	Explicitly answers both 'what' (the full build→fuzz→triage→MRE→bisect→report pipeline) and 'when' ('Use when the user says ...', 'Triggers whenever the user points at a PG source dir and wants to hunt bugs') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms and bilingual variants — 'find a bug in postgres', 'fuzz postgres', 'hunt for a crash', 'test a recent commit', 'write a repro', 'bisect this crash', plus Chinese forms — covering what a user would actually say.	5 / 5
Distinctiveness Conflict Risk	A clear niche — crash-first bug-hunting in a local PostgreSQL source tree via a poisoned-build fuzzing pipeline — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: digoal/blog
Path: skills/find-postgres-bug/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.