ISSTA Skills

A 12-skill depth pack for ISSTA submissions: routing testing-and-analysis work into the SIGSOFT venue, HotCRP double-anonymous submission checks, the major-revision review cycle, author response, ACM-badged artifact evaluation, reproducibility, replication packages, review process, writing style, related work, benchmark-driven experiments, and the campaign workflow. Grounded in the official ISSTA

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/issta-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-issta-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Issta Workflow · brycewang-stanford
Use when planning an ISSTA project timeline from venue fit through the January research-paper deadline, the March author response, the April first decision, the May Major-Revision sprint, the June final decision, artifact evaluation, and the October symposium, with backward-planning offsets for a testing/analysis tool paper and its artifact.

1k repo stars
▌
Issta Submission · brycewang-stanford
Use when auditing an ISSTA submission for HotCRP readiness, the 18-page (excluding references) limit, ACM sigconf plus review and anonymous formatting, double-anonymous integrity, the January deadline, artifact intent, track choice among research/experience/replicability, and desk-reject triggers before the phase-one upload.

1k repo stars
▌
Issta Experiments · brycewang-stanford
Use when designing or auditing ISSTA experiments, covering real subject programs and benchmarks like Defects4J, fair tool-baseline configuration, bug-finding and coverage metrics, non-parametric comparison with effect sizes, equal-budget protocols, repeated runs, and matching evidence to the claim being made.

1k repo stars
▌
Issta Camera Ready · brycewang-stanford
Use when preparing an accepted ISSTA paper for the ACM Digital Library camera-ready, covering de-anonymization, the final ACM sigconf layout without the review/anonymous options, ACM rights forms and DOI, metadata and CCS concepts, the artifact DOI and badge display, registration, and the in-person presentation obligation.

1k repo stars
▌
Issta Related Work · brycewang-stanford
Use when positioning an ISSTA submission against the testing and analysis literature, covering the sibling venues (ICSE, FSE, ASE, ICST, PLDI, CAV), delta-first framing against the nearest technique, double-anonymous self-citation, distinguishing the closest tool baseline, and avoiding the venue-confusion of citing a paper to the wrong conference.

1k repo stars
▌
Issta Supplementary · brycewang-stanford
Use when deciding what lives in the ISSTA 18-page body versus the artifact and any appendix, covering the no-unlimited-appendix reality, what reviewers will and will not open, splitting a testing/analysis paper between body and package, anonymity of supplementary material, and keeping decision-critical evidence inside the reviewed pages.

1k repo stars
▌
Issta Writing Style · brycewang-stanford
Use when revising an ISSTA paper for a clear testing/analysis contribution, covering the threat-model-then-technique structure, the evaluation contract, a threats-to-validity section that is not boilerplate, claims scoped to the subjects tested, double-anonymous phrasing, and 18-page ACM sigconf discipline that survives specialist reviewers.

1k repo stars
▌
Issta Review Process · brycewang-stanford
Use when explaining or planning around ISSTA peer review, covering double-anonymous reviewing, at least three PC reviews, the Accept/Major-Revision/Reject outcome model, the phase-two major-revision resubmission, the named evaluation criteria, how the decision is actually synthesized, and how earlier editions ran multiple rolling deadlines.

1k repo stars
▌
Issta Author Response · brycewang-stanford
Use when drafting an ISSTA author response for the rebuttal window or planning a Major-Revision resubmission, covering evidence-anchored replies, the Accept/Major-Revision/Reject outcome model, converting reviewer asks into a revision ledger, anonymity in the response, and the difference between a rebuttal claim and a promised change.

1k repo stars
▌
Issta Reproducibility · brycewang-stanford
Use when strengthening ISSTA reproducibility and verifiability evidence, covering pinned subject programs and benchmark versions, random seeds and timeout budgets, non-determinism disclosure for fuzzing and analysis, claim-to-evidence traceability, tool availability statements, and keeping the artifact consistent with the paper's tables.

1k repo stars
▌
Issta Topic Selection · brycewang-stanford
Use when deciding whether a project is a strong ISSTA fit versus ICSE, FSE, ASE, ICST, PLDI/CAV, or an SE journal, identifying whether the contribution is a testing/analysis technique, characterizing its evaluation shape, and sharpening the framing before writing begins.

1k repo stars
▌
Issta Artifact Evaluation · brycewang-stanford
Use when packaging an ISSTA tool, benchmark, and results for the artifact-evaluation track, covering the ACM badges (Artifacts Available via Zenodo, Evaluated Functional and Reusable, Results Reproduced), the anonymous review-time copy, containerization, a runnable entry point, and what ISSTA artifact evaluators actually try first.

1k repo stars