ppopp-review-process
Use when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer matching, the author-response rebuttal, the accept/reject decision with automatic poster consideration, and how PPoPP's process differs from PLDI's and CGO's.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-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.
# PPoPP Review Process Model the pipeline before interpreting any single review. PPoPP runs a **single-round, double-blind conference review** with a **scheduled author-response rebuttal** and an unusual safety net: papers not accepted for a talk are **automatically considered for posters**. The most consequential mental shift for authors arriving from a journal-style venue is that there is (as verified) no guaranteed revise-and-resubmit round — the rebuttal is your one written turn, so it must land. ## Process model - Submission and review run on **HotCRP** with **double-blind** anonymity: author identities are hidden from reviewers and reviewer identities from authors. - Papers are read by the **Program Committee** and an **External/Extended Review Committee (ERC)**; declare conflicts against **both** pools. Reviewer assignment may use the **Toronto Paper Matching System (TPMS)**, so your abstract and topic tags shape who reads you. - After the initial reviews there is a fixed **author-response period** (PPoPP 2026: 27–29 October 2025). Authors respond within a word cap; reviewers then discuss and decide. - The primary decision is **accept / reject** for a regular presentation. W
- Process model
- What PPoPP reviewers weigh
- Reading a decision
- How PPoPP differs from its siblings
- Where author leverage actually exists
- Reading a review packet
- Misreadings to avoid
- Output format
What does the ppopp-review-process skill do?
Use when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer matching, the author-response rebuttal, the accept/reject decision with automatic poster consideration, and how PPoPP's process differs from PLDI's and CGO's.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-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.