ICSME Skills

A 12-skill depth pack for IEEE ICSME (International Conference on Software Maintenance and Evolution): routing a maintenance/evolution paper among the SE venues, the single-round research track with its early-decision cut and author-response rebuttal, double-anonymous EasyChair submission on the IEEEtran two-column 10+2 budget, the Journal-First (J1C2) and Registered Reports and RENE tracks, minin

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/icsme-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-icsme-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

▌
Icsme Workflow · brycewang-stanford
Use when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.

1k repo stars
▌
Icsme Submission · brycewang-stanford
Use when auditing an IEEE ICSME research-track submission for EasyChair readiness, covering the abstract-then-paper two-step deadline, the IEEEtran two-column 10+2 page budget, double-anonymous review, the open-science data-availability expectation, and desk-reject triage before the AoE cutoff.

1k repo stars
▌
Icsme Experiments · brycewang-stanford
Use when designing or auditing IEEE ICSME empirical evaluations, covering real evolving subject systems, mining-software-repositories provenance, fair baselines, SE-standard statistics and effect sizes, change-history and survivorship confounds, qualitative rigor, contamination-aware LLM ablations, and matching evidence to the shape of each maintenance/evolution claim.

1k repo stars
▌
Icsme Camera Ready · brycewang-stanford
Use when preparing an accepted IEEE ICSME paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran two-column format and page budget, the IEEE eCopyright form, integrating the reviewer-required and author-response changes without scope creep, permanentizing data-availability links, and the ROSE-Festival artifact handoff.

1k repo stars
▌
Icsme Related Work · brycewang-stanford
Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.

1k repo stars
▌
Icsme Supplementary · brycewang-stanford
Use when deciding what belongs in an IEEE ICSME paper body versus its anonymized artifact and appendices, covering the IEEEtran two-column 10-page budget where figures and appendices count, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split a mining/evolution paper between body and package.

1k repo stars
▌
Icsme Writing Style · brycewang-stanford
Use when revising an IEEE ICSME paper for a maintenance/evolution contribution stated on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the IEEEtran two-column 10-page budget.

1k repo stars
▌
Icsme Review Process · brycewang-stanford
Use when reasoning about how an IEEE ICSME research submission is evaluated, covering double-anonymous review, the early-decision cut that issues Accept/Reject before the rebuttal, the "Response Recommended" author-response period, the single-round accept/reject model with no Major Revision, and how ICSME's process differs from FSE's journal-style round and ICSE's cycles.

1k repo stars
▌
Icsme Author Response · brycewang-stanford
Use when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all, answering the PC's specific "Response Recommended" questions with existing evidence, staying anonymous, and doing it in one round with no Major Revision safety net.

1k repo stars
▌
Icsme Reproducibility · brycewang-stanford
Use when strengthening IEEE ICSME reproducibility and open-science evidence, covering the data-availability statement, anonymized-but-runnable artifacts, mining and LLM provenance pinning, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between the paper and the artifact ahead of the ROSE-Festival IEEE badges.

1k repo stars
▌
Icsme Topic Selection · brycewang-stanford
Use when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring, mining software repositories) or should be routed to ICSE, FSE, ASE, ISSTA, MSR, SANER, SCAM, or an SE journal (TSE/EMSE), and when to use ICSME's Journal-First, Registered Reports, or RENE tracks instead of the research track.

1k repo stars
▌
Icsme Artifact Evaluation · brycewang-stanford
Use when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed" badges, what evaluators check first, DOI-issuing archives, evaluator-proof documentation, the shared track with SCAM and VISSOFT, and the separate post-acceptance deadline.

1k repo stars