oopsla-related-work
Use when building an OOPSLA related-work section — positioning against the PACMPL family (POPL, PLDI, ICFP, OOPSLA itself) plus ECOOP, Onward!, and SE venues, citing journal-era OOPSLA papers in PACMPL volume/issue form, verifying every venue attribution on dblp, and stating per-line technical deltas.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-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.
# OOPSLA Related Work OOPSLA sits inside a family that shares authors and reviewers: POPL, PLDI, ICFP publish in the same PACMPL journal, ECOOP is the adjacent European OO venue, Onward! shares the SPLASH building, and ICSE/FSE/ISSTA overlap on empirical software questions — ISSTA was literally co-located with SPLASH 2026. The related-work section is therefore written for people who may have *authored* the cited lines, and who will meet your paper again if a revision round occurs. Two failure modes dominate: venue misattribution and delta-free citation lists. ## Citation form in the journal era Since OOPSLA became a PACMPL track, its papers are journal articles and must be cited as such: ```bibtex @article{belyakova2020worldage, author = {Belyakova, Julia and Chung, Benjamin and Gelinas, Jack and Nash, Jameson and Tate, Ross and Vitek, Jan}, title = {World Age in Julia: Optimizing Method Dispatch in the Presence of Eval}, journal = {Proc. ACM Program. Lang.}, volume = {4}, number = {OOPSLA}, articleno = {207}, year = {2020}, doi = {10.1145/3428275} } ``` Recent volumes split into OOPSLA1 and OOPSLA2 issues — preserve the issue name (`number = {OOPSLA1}`) exactly as the ACM DL recor
- Citation form in the journal era
- Verification discipline
- Deltas, not inventories
- Coverage strategy
- Output format
What does the oopsla-related-work skill do?
Use when building an OOPSLA related-work section — positioning against the PACMPL family (POPL, PLDI, ICFP, OOPSLA itself) plus ECOOP, Onward!, and SE venues, citing journal-era OOPSLA papers in PACMPL volume/issue form, verifying every venue attribution on dblp, and stating per-line technical deltas.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-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.