ase-topic-selection
Use when deciding whether a software-engineering project belongs at ASE (IEEE/ACM Automated Software Engineering) or should be routed to ICSE, ESEC/FSE, ISSTA, a PL venue, or an SE journal, and when distinguishing ASE by its automation-centric contribution shape, its tool/technique emphasis, and its AI4SE/SE4AI scope.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-topic-selection --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.
# ASE Topic Selection Decide the venue before drafting. ASE — the **IEEE/ACM International Conference on Automated Software Engineering** — is the home for research that **automates** software-engineering tasks: the analysis, design, implementation, testing, comprehension, and maintenance of software, and increasingly the two-way street of AI for SE and SE for AI. Its reviewers read for a **technique or tool that automates something**, evaluated on real subjects. A paper whose real center is a broad empirical observation, a testing-theory result, or a pure ML advance is respected and then rejected as off-center. ## The routing question that matters most The decisive ASE question is not "is this SE?" but **"is the contribution an *automation* — a technique or tool that does an SE task a human or a weaker tool did before?"** If the beating heart of the paper is a new automated mechanism (an analysis, a generator, a synthesizer, a repair technique, a learned model applied to an SE task), ASE is a natural home. If the heart is a finding, a theory, or a measurement study, a sibling fits better — even when the topic overlaps. ## Sibling-venue routing table | Signal in your project | Bett
- The routing question that matters most
- Sibling-venue routing table
- Contribution shapes ASE rewards
- The model-swap and re-label tests
- Which co-located track fits
- Cheap reconnaissance before committing
- Decision procedure
What does the ase-topic-selection skill do?
Use when deciding whether a software-engineering project belongs at ASE (IEEE/ACM Automated Software Engineering) or should be routed to ICSE, ESEC/FSE, ISSTA, a PL venue, or an SE journal, and when distinguishing ASE by its automation-centric contribution shape, its tool/technique emphasis, and its AI4SE/SE4AI scope.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-topic-selection --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.