Individual skill
icsme-topic-selection
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.
ICSME-Skills/skills/icsme-topic-selection/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- 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,410
- 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
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# ICSME Topic Selection
Decide the venue before drafting. ICSME — the IEEE International Conference on Software
Maintenance and Evolution — is the field's dedicated home for what happens to software *after*
the first release: maintaining it, evolving it, comprehending it, refactoring it, repaying its
technical debt, and mining the repositories that record its history. A brilliant paper about a
*greenfield* synthesis technique, a novel type system, or a pure ML model is respected and then
rejected as out of scope. The ICSME question is not "is this good SE?" but **"is the paper's
centre of gravity a real maintenance-or-evolution problem?"**
## The routing question that matters most
ICSME overlaps ICSE and FSE (both take maintenance work) and SANER, SCAM, MSR, and ICPC (all
maintenance-adjacent). The decisive test is **which community the paper is arguing with** and