ase-related-work
Use 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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-related-work --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 Related Work Position the paper against **prior automation**, not against a topic. At ASE the question a reviewer holds is "what does this tool/technique do that the existing automated approaches do not?" — so related work is a **delta argument**, and the strongest deltas are stated against named, runnable prior tools you can (and often must) compare against empirically. ## Cover the ASE literature lanes An automated-SE paper usually sits at the intersection of several lanes; name your position in each that applies: - **Program analysis** — static/dynamic analysis, symbolic/concolic execution, abstract interpretation, invariant inference. - **Test generation and testing** — search-based, specification-based, fuzzing, regression and flaky-test handling. - **Fault localization, debugging, and repair** — spectrum-based localization, automated program repair, patch synthesis. - **Synthesis and recommendation** — program/code synthesis, API recommendation, refactoring automation. - **Comprehension and documentation** — summarization, code search, clone and change analysis. - **Learning-based / AI4SE** — learned code representations, models applied to SE tasks, LLM-based automation
- Cover the ASE literature lanes
- Delta-first positioning
- Fair head-to-head framing (the ASE credibility test)
- Distinguish ASE from sibling-venue prior work
- Double-anonymous self-citation
- Coverage checks
- Output format
What does the ase-related-work skill do?
Use 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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-related-work --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.