ICSE Skills

A 12-skill depth pack for the IEEE/ACM International Conference on Software Engineering (ICSE): venue fit, HotCRP submission audits, the Accept/Major-Revision/Reject decision model, author response, camera-ready, artifact evaluation and ACM badges, open-science and verifiability evidence, empirical rigor, related work, and cycle management. Grounded in the official ICSE 2027 Research Track call, i

by @brycewang-stanford 11 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/icse-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 11 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-icse-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: 11
authors: 1

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

Skills in this plugin

▌
Icse Submission · brycewang-stanford
Use when auditing an ICSE research-track submission for HotCRP readiness, covering the mandatory abstract deadline, the 10-page-plus-2-reference-page IEEE format, double-anonymous rules, the open-science Data Availability section, supplementary uploads, and desk-reject triage before the AoE cutoff.

1k repo stars
▌
Icse Experiments · brycewang-stanford
Use when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based techniques, and threats-driven study design.

1k repo stars
▌
Icse Camera Ready · brycewang-stanford
Use when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data Availability section with archival DOIs, IEEE-template production checks, and conference-presentation obligations to verify.

1k repo stars
▌
Icse Related Work · brycewang-stanford
Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.

1k repo stars
▌
Icse Supplementary · brycewang-stanford
Use when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized supplementary links and HotCRP uploads, package organization for reviewer navigation, and content-placement rules that protect the review.

1k repo stars
▌
Icse Writing Style · brycewang-stanford
Use when writing or revising an ICSE research-track paper, covering empirical-SE paper anatomy, research questions as the load-bearing structure, the threats-to-validity section the community expects, practitioner-grounded motivation, calibrated claims, and fitting a complete study into ten IEEE pages.

1k repo stars
▌
Icse Review Process · brycewang-stanford
Use when reasoning about how an ICSE research-track submission is evaluated, covering double-anonymous PC review, the four posted criteria, the Accept / Major Revision / Reject decision model, the revision-and-final-decision timeline, and what recent ICSE acceptance statistics imply for strategy.

1k repo stars
▌
Icse Author Response · brycewang-stanford
Use when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the four-week revision sprint to the November deadline, response-letter structure, and change tracking that survives PC re-review.

1k repo stars
▌
Icse Reproducibility · brycewang-stanford
Use when building the verifiability story of an ICSE research-track paper, covering the open-science policy's sharing-by-default expectation, the Data Availability section, anonymized replication packages at review time, provenance pinning for mining and LLM studies, and honest non-sharing justifications.

1k repo stars
▌
Icse Topic Selection · brycewang-stanford
Use when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE co-located track such as NIER, SEIP, SEIS, or Demonstrations, based on contribution type, evidence maturity, and audience.

1k repo stars
▌
Icse Artifact Evaluation · brycewang-stanford
Use when preparing an artifact for the ICSE Artifact Evaluation track after paper acceptance, covering the ACM badge system (Available, Reusable, Results Reproduced/Replicated), evaluator-proof packaging, archival requirements, open licensing, and the January-window timeline anchored to recent cycles.

1k repo stars