fse-camera-ready
Use when preparing an accepted ESEC/FSE paper for its PACMSE camera-ready, covering de-anonymization, the ACM Primary Article Template and PACMSE journal metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing the Data Availability links, and the ACM artifact-badge handoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-camera-ready --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 Camera Ready Use this after acceptance. FSE research papers are published as **PACMSE journal articles**, so the camera-ready is a journal production step, not just a formatting pass. Reopen the current PACMSE author instructions, the decision email, and the artifact-track and registration pages before advising. ## Camera-ready audit - **De-anonymize completely:** restore the author block, affiliations, acknowledgements, funding, and the real tool and repository names that heavy double-anonymity forced you to hide. - **Apply the final format:** the ACM Primary Article Template, within the current page budget, with the camera-ready allowances the acceptance letter states. - **Complete PACMSE journal metadata:** title/abstract, author order, ORCIDs, ACM CCS concepts and keywords, and the DOI-bearing citation once assigned. Journal metadata errors are harder to fix after publication than conference ones. - **Integrate reviewer-required changes** from the reviews and any Major Revision faithfully — without strengthening claims beyond what was evaluated. - **Permanentize open science:** replace every anonymized artifact link with a public, licensed, DOI-issuing archive, and update
- Camera-ready audit
- De-anonymization sweep
- PACMSE production checks
- Worked example: integrating a Major Revision fix
- Artifact-badge handoff
- Hedged logistics
- Output format
What does the fse-camera-ready skill do?
Use when preparing an accepted ESEC/FSE paper for its PACMSE camera-ready, covering de-anonymization, the ACM Primary Article Template and PACMSE journal metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing the Data Availability links, and the ACM artifact-badge handoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-camera-ready --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.