icse-submission
Use when auditing an ICSE research-track submission for HotCRP readiness, covering the mandatory abstract deadline, the 10-page-plus-2-reference-page IEEE format, double-anonymous rules, the open-science Data Availability section, supplementary uploads, and desk-reject triage before the AoE cutoff.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-submission --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.
# ICSE Submission Run this audit before touching the submit button on the ICSE HotCRP site. Every number below was read from the ICSE 2027 Research Track pages on 2026-07-08 (via search renderings of the official `conf.researchr.org` URLs — see `resources/official-source-map.md`); treat them as one cycle's snapshot and reopen the live call before acting. ## The 2027-cycle mechanics - **Two deadlines, both AoE (23:59:59, UTC-12).** The abstract deadline (June 23, 2026) is *mandatory* — no abstract in HotCRP by that date, no paper submission a week later (June 30, 2026). ICSE uses the abstract for bidding and PC assignment, so a placeholder abstract that drifts from the final paper quietly damages your reviewer match. - **10 + 2 page format.** Main text ≤ 10 pages *inclusive of all figures, tables, and appendices*; up to 2 additional pages may contain **only references**. There is no unlimited appendix: anything reviewers must see lives inside the 10. - **IEEE conference template, unmodified.** Title in 24pt, body in 10pt — `\documentclass[10pt,conference]{IEEEtran}`, without `compsoc` options. The call states that spacing/font alterations can mean desk rejection without review. - **
- The 2027-cycle mechanics
- Double-anonymous sweep
- Open science at submission time
- Desk-risk triage
- Final-week order of operations
- What the form asks that the paper does not
- IEEEtran traps that surface at upload
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any supplementary archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|acknowledg|grant' | head unzip -l supplement.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head grep -rn "university\|@.*\.edu" supplement/ --include='*.md' | head
What does the icse-submission skill do?
Use when auditing an ICSE research-track submission for HotCRP readiness, covering the mandatory abstract deadline, the 10-page-plus-2-reference-page IEEE format, double-anonymous rules, the open-science Data Availability section, supplementary uploads, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-submission --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.