sigmod-review-process
Use when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-review-process --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.
# SIGMOD Review Process A SIGMOD research submission enters a journal pipeline with a conference cadence: papers submitted to a PACMMOD round are reviewed double-anonymously through Microsoft CMT, authors get a mid-round feedback window, and the first verdict is three-valued — accept, reject, or revise. Understanding which lever moves which outcome is most of review-stage strategy. Mechanics shift
What does the sigmod-review-process skill do?
Use when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-review-process --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.