Individual skill
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.
ICSME-Skills/skills/icsme-related-work/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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?