pldi-review-process
Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL publication follow the decision.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-review-process --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 Review Process Model the pipeline from the 2026 cycle (pldi26.sigplan.org, read 2026-07-08), then re-anchor every date to the current edition: papers due November 13, 2025; reviews written over the winter; author response February 17-21, 2026; decisions March 5, 2026; artifact evaluation after acceptance; publication as PACMPL Issue PLDI; talks in Boulder June 17-19, 2026. Chairs rotate per edition — 2026 ran under Program Chair Manu Sridharan — so process details are one-cycle facts. ## Who is reading you The PC is dominated by people who have shipped compilers, runtimes, analyzers, and verifiers. Practical consequences: - **Claims are audited mechanically.** A reviewer may re-derive your complexity bound, check your semantics against a corner case, or mentally rerun your benchmark protocol. Vague spots read as hidden flaws. - **"Would this survive contact with real programs?"** is the ambient question. Toy-language-only evaluations need an explicit argument for why the toy captures the hard part. - **Double-blind is real but statistical**: some reviewers will guess your lab; the process still requires the paper not to confirm it. ## Stage-by-stage | Stage (2026 anchors) |
- Who is reading you
- Stage-by-stage
- Distinguished papers
- Reading a decision
- Output format
What does the pldi-review-process skill do?
Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL publication follow the decision.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-review-process --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.