Individual skill
issta-topic-selection
Use when deciding whether a project is a strong ISSTA fit versus ICSE, FSE, ASE, ICST, PLDI/CAV, or an SE journal, identifying whether the contribution is a testing/analysis technique, characterizing its evaluation shape, and sharpening the framing before writing begins.
ISSTA-Skills/skills/issta-topic-selection/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- writing Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,433 bytes
Read excerpt
# ISSTA Topic Selection
Use this before writing. ISSTA is the venue for techniques that **test or analyze software** — that
find, characterize, or reason about program behaviour and defects — evaluated on real subjects. The
routing decision is mostly about whether that is the *core* of the contribution, or an ingredient in
something broader.
## Fit test
- Prefer ISSTA when the contribution is a testing or analysis technique: test generation, fuzzing,
symbolic or concolic execution, static/dynamic analysis, fault localization, program-repair
evaluation, sanitizers, or an empirical study *about* testing and analysis.
- Route to **ICSE or FSE** when the contribution is broader software engineering: requirements,
design, process, developer studies, or a technique whose testing angle is secondary. These are