find-postgres-bug
find-postgres-bug is a Bug triage & fixing skill for AI agents, published by digoal in the blog repository on GitHub. Skillspace rates find-postgres-bug D (69/100) and it passed the safety scan; the rating is based on static analysis only.
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.
- Grade
- D
- Quality
- 69 / 100
- Safety
- Passed
- GitHub stars
- 8,528
Unproven: rated by static analysis only, not yet compared head-to-head.
Our two independent classifiers differ on this skill's category, so treat the placement as provisional.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 78 / 100
- Maturity
- Structured: ships references or scripts
- Security scan
- No issues found
- License
- GPL-2.0
- Adoption
- Adopted by 0 other repositories, in 0 collections
- Scope
- Vendor-specific: built around one product. Bug hunting in PostgreSQL, a public product, from an unrelated blog repo
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.