pldi-submission
Use when auditing a PLDI submission for HotCRP readiness — the single annual November deadline, the 20-pages-of-text-excluding-bibliography cap in single-column acmsmall format, double-blind hygiene across tool names and repositories, dual-submission rules, and summary-rejection triggers before the cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-submission --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 Submission Run this audit before the upload, not after. The numbers below were read from the PLDI 2026 Call for Papers and track pages on 2026-07-08 (via search renderings of the official URLs — see `resources/official-source-map.md`); they describe one cycle and must be rechecked against the live CFP for the cycle you are entering. The PLDI 2027 call was not yet posted at that date. ## The 2026-cycle mechanics - **One deadline a year.** PLDI 2026 papers were due Thursday, November 13, 2025. There is no second round; a missed November costs twelve months. - **HotCRP, not OpenReview.** Submission ran at `pldi2026.hotcrp.com` — profile, conflicts, and topic areas live there, and each edition gets a fresh instance. - **Page budget: at most 20 pages of *text*, excluding bibliography**, in the single-column ACM `acmsmall` layout (10 pt font, 12 pt line spacing, text block 5.478 in x 7.884 in), the format PACMPL publishes in. Build with `sample-acmsmall-conf.tex` from the acmart package. - **Summary rejection is the stated penalty** for a different format — smaller fonts, a larger text block, squeezed spacing. The chairs do not negotiate margins. - **Double-blind**, and PLDI has u
- The 2026-cycle mechanics
- Where PL papers leak identity
- Summary-rejection and triage table
- Final week, in order
- What this cycle did not settle (待核实)
- Output format
pdfinfo paper.pdf | grep -Ei 'author|creator' pdftotext paper.pdf - | grep -niE 'github\.com/[^ ]+|gitlab|acknowledg|grant no' | head unzip -l supplement.zip | grep -Ei '\.git/|/home/|/Users/' | head
What does the pldi-submission skill do?
Use when auditing a PLDI submission for HotCRP readiness — the single annual November deadline, the 20-pages-of-text-excluding-bibliography cap in single-column acmsmall format, double-blind hygiene across tool names and repositories, dual-submission rules, and summary-rejection triggers before the cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-submission --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 984 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.