Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/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.
Passed 22 of 22 test cases with the skill, and 16 of 22 without it.
and 3 more in the full report
6 fixed16 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
According to standard SE venue decision procedures, what primary question should be asked regarding the target audience before deciding to draft a paper for ASE?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the key audience question: whether SE developers, testers, maintainers, or tool-builders will run the automation | Missed | Passed |
The instructions your model reads when the skill loads.
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 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.
| Signal in your project | Better home | Why |
|---|---|---|
| Core is a technique/tool that automates an SE task, evaluated on real systems | ASE | Automated software engineering is its named center; dual IEEE/ACM, IEEE-Xplore+ACM-DL proceedings |
| Broad empirical or foundational SE contribution; the lesson is a finding, not a tool | ESEC/FSE | The general-SE flagship; PACMSE journal model, empirical breadth |
| Equally broad SE technique, but ICSE's cycle/stage fits and you want its reach | ICSE | The other general-SE flagship; different calendar and (IEEE-side) format |
| Depth in testing theory, program analysis foundations, or fault detection | ISSTA | Deeper testing/analysis expertise, round-based reviewing |
| The automated mechanism is a program-language/compiler advance | PLDI / OOPSLA / POPL | PL venues own the language-mechanism contribution |
| The contribution is a new model/architecture; the SE task is a benchmark | an ML venue | Model-as-contribution routes out of SE |
| Study too long or too nuanced for the page budget | TSE / TOSEM / EMSE | Journals with no page ceiling; some feed ASE's Journal-First track |
test cases passed, vs 16 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.