pldi-skills

Plugin pldi-skills from marketplace awesome-journal-skills in brycewang-stanford/Awesome-Journal-Skills. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• pldi-artifact-evaluation

  Use when packaging a PLDI artifact for the post-acceptance evaluation — earning the Functional, Reusable, and Available badges, archiving a DOI-stamped snapshot on Zenodo, containerizing toolchains and benchmark suites, and writing a README an evaluator can follow in a fresh VM.

• 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.

• pldi-camera-ready

  Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June conference presentation.

• pldi-experiments

  Use when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed mechanism, and scoping claims to the platforms mea

• pldi-related-work

  Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.

• pldi-reproducibility

  Use when hardening a PLDI paper's measurements against the SIGPLAN Empirical Evaluation Guidelines — warmup and steady-state discipline, variance and confidence reporting, principled benchmark choice, pinned toolchains, cross-platform validity, and a measurement log that survives artifact evaluation

• 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.

• 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

• pldi-supplementary

  Use when deciding what accompanies a PLDI submission beyond the 20 text pages — full proofs, extended benchmark data, anonymized code — and how to keep every extra byte double-blind, optional for reviewers, and consistent with the main PDF under summary-rejection formatting rules.

• pldi-topic-selection

  Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.

• pldi-workflow

  Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.

• pldi-writing-style

  Use when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest limitation statements, and prose that fits the single-column acmsmall journal format without padding toward the page cap.

Similar plugins