ASE Skills
Twelve ASE-specific skills for the IEEE/ACM International Conference on Automated Software Engineering and its automated-SE research track, grounded in the ASE 2025/2026 researchr calls, the ase26.hotcrp.com submission site, IEEE Xplore, the ACM Digital Library, and dblp.
Skills in this plugin
12- ▌ Ase Workflow · brycewang-stanfordUse when planning an ASE (IEEE/ACM Automated Software Engineering) research-track campaign backward from the deadline, through abstract registration, the double-anonymous submission, the early-rejection gate, rebuttal, the criteria-bound revision round, artifact evaluation, and the camera-ready in both IEEE Xplore and the ACM Digital Library.
- ▌ Ase Camera Ready · brycewang-stanfordUse when preparing the ASE (IEEE/ACM Automated Software Engineering) camera-ready after acceptance or a successful revision, covering systematic de-anonymization, the extra content page, the mandatory Data Availability finalization, the correct IEEE/ACM template and metadata, permanentized artifact links, and dual IEEE-Xplore/ACM-DL production checks.
- ▌ Ase Submission · brycewang-stanfordUse when auditing an ASE (IEEE/ACM Automated Software Engineering) research-track submission for HotCRP readiness, covering the ACM acmart sigconf template and the 10+2 page budget, double-anonymous review, the mandatory Data Availability Statement, the early-rejection stage before rebuttal, and desk-reject triage before the deadline.
- ▌ Ase Related Work · brycewang-stanfordUse when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning against prior tools/techniques, fair head-to-head framing, and double-anonymous self-citation.
- ▌ Ase Experiments · brycewang-stanfordUse when designing or auditing the evaluation of an ASE (IEEE/ACM Automated Software Engineering) paper, covering real subject systems, fair runnable tool baselines, task-matched effectiveness metrics, ablations that isolate a learned component, oracle and correctness validation, contamination-aware LLM handling, and provenance for mining.
- ▌ Ase Supplementary · brycewang-stanfordUse when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.
- ▌ Ase Writing Style · brycewang-stanfordUse when shaping the prose and structure of an ASE (IEEE/ACM Automated Software Engineering) research paper, covering the automation-first first-page arc, stating the automated task precisely, keeping the tool runnable and the model-swap test in mind, threats-as-argument, and the 10+2 page discipline on the ACM acmart template.
- ▌ Ase Review Process · brycewang-stanfordUse when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from FSE's PACMSE Major Revision, ICSE's cycles, and ISSTA's rounds.
- ▌ Ase Author Response · brycewang-stanfordUse when drafting ASE (IEEE/ACM Automated Software Engineering) author responses, covering the double-anonymous rebuttal that must first survive the early-rejection gate and — distinctively — the criteria-bound revision-round summary-of-changes that maps every stated revision criterion to a concrete change and is re-checked against those criteria.
- ▌ Ase Reproducibility · brycewang-stanfordUse when building the open-science and reproducibility story for an ASE (IEEE/ACM Automated Software Engineering) submission, covering the mandatory Data Availability Statement, anonymized-but-runnable tools, tool and subject-system provenance pinning, cached LLM outputs, and staging for the ACM Available/Reusable artifact badges.
- ▌ Ase Topic Selection · brycewang-stanfordUse 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.
- ▌ Ase Artifact Evaluation · brycewang-stanfordUse when preparing an accepted ASE (IEEE/ACM Automated Software Engineering) paper's tool and data for the Artifact Evaluation track, targeting the ACM Artifacts Available and Artifacts Reusable badges on the track's own deadline, with the badge shown on the paper's front page in both IEEE Xplore and the ACM Digital Library.