fse-related-work
Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-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.
# FSE Related Work Use this to audit novelty and eligibility. FSE reviewers are close to the SE literature and expect to see where your paper sits relative to the nearest prior work — stated as a **delta**, not a list. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising authors. ## Positioning checks - **Separate the software-engineering novelty from the engineering effort.** What is new: a technique, an empirical finding, a validated measurement, a design, or an evidence regime nobody had covered? - **Cover the SE lanes.** FSE reviewers expect the flagship venues and the journals, not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware. - **Write delta-first.** Each closely related paper gets one sentence naming what it did and one naming what you do differently — not a summary. Position, don't catalog. - **Preserve heavy double-anonymity.** Cite your own prior work in the third person and never link reviewers to an identity-revealing preprint, repository, or homepage. - **Declare overlap** with any prior conference/workshop version or concurrent submission; do not re-
- Positioning checks
- SE literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the fse-related-work skill do?
Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-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.