pldi-author-response
Use when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions without promising new systems work.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-author-response --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 Author Response PLDI 2026 gave authors a five-day response window, February 17-21, 2026, between review delivery and the March 5 notification (dates from `pldi26.sigplan.org`, read 2026-07-08; every cycle re-times this). The response is read by people who build compilers and verifiers for a living: precision beats rhetoric, and a pointer into your own submitted PDF beats a paragraph of reassurance. ## Triage before writing Sort every reviewer point into one of four buckets and answer them in this order: | Bucket | Example at PLDI | Correct move | |---|---|---| | Factual error | "The analysis ignores exceptions" when §4.2 handles them | Quote §4.2 verbatim, one sentence of context | | Soundness doubt | "Theorem 2 seems to assume no reentrancy" | State the assumption's exact location; if the reviewer is right, say what the fix costs | | Evaluation gap | "No comparison against the LLVM baseline at -O2" | Give the number if it exists in your logs; otherwise commit to the exact experiment, not to "more evaluation" | | Scope disagreement | "Why not handle JIT compilation?" | Defend the stated scope; do not promise to widen it | A soundness doubt outranks everything. One reviewer c
- Triage before writing
- Rules that keep responses alive
- A working skeleton
- After the window
- Output format
What does the pldi-author-response skill do?
Use when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions without promising new systems work.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-author-response --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.