icsme-related-work
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-related-work --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.
# ICSME Related Work Use this to audit novelty and eligibility. ICSME reviewers are close to the maintenance/evolution literature and expect to see where your paper sits relative to the nearest prior work — stated as a **delta**, not a list. Because the venue values replication (the RENE track) and rewards honest re-examination, "we redo prior work" is a legitimate contribution *when framed as one* — but it must engage the original explicitly. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising. ## Positioning checks - **Separate the maintenance/evolution novelty from the engineering effort.** What is new: a technique, an empirical finding about how software ages, a validated measurement of debt or comprehension, a recovered model, or an evidence regime nobody had covered? - **Cover the maintenance lanes.** ICSME reviewers expect the evolution venues and journals, not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware of the community. - **Write delta-first.** Each closely related paper gets one sentence naming what it did and one naming what you do differently — not a
- Positioning checks
- Maintenance literature lanes
- Delta-first positioning vignette
- Replication and prior-version judgment calls
- Eligibility red flags
- Output format
What does the icsme-related-work skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-related-work --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 909 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.