pldi-related-work
Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-related-work --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PLDI Related Work At PLDI, related work is an adversarial exercise: your reviewers are frequently the authors of your closest baselines. The section must therefore do two things — prove you know the landscape's *mechanisms* (not just its citations), and state, line by line, what this paper does that each prior technique cannot. ## The delta discipline Ban survey sentences ("Much work has studied pointer analysis [3,7,12,19]"). Every citation earns its place with a mechanism and a delta: > Steensgaard-style unification [7] scales linearly but merges all callees' > effects; our signatures keep callee effects separate at equal asymptotic cost > (§4.3). If you cannot write the delta clause, you have not read the paper closely enough to cite it at PLDI — where the cited author may be reviewer B. ## Coverage map | Neighbor | What to check there | Typical relationship to a PLDI paper | |---|---|---| | PLDI, last ~4 cycles | The direct competition; reviewers expect these compared, not just cited | Baseline or head-to-head | | POPL | The semantic foundations your system builds on | "We implement/scale what [x] formalized" | | OOPSLA | Language design, empirical SE-flavored PL studies | Al
- The delta discipline
- Coverage map
- Cite the PACMPL era correctly
- Verification before submission
- Output format
What does the pldi-related-work skill do?
Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-related-work --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.