Review Pending PR Reviews
nrwl/nx
Review, grill, edit, and post pending PR review drafts saved by /review-pr (or its batch/cron runners).
A skill your agent uses when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance…
MITAuto-check passed
Install Osdi Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/OSDI-Skills/skills/osdi-review-process .claude/skills/osdi-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "osdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-process into .claude/skills/osdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/OSDI-Skills/skills/osdi-review-process .agents/skills/osdi-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "osdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-process into .agents/skills/osdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/OSDI-Skills/skills/osdi-review-process .cursor/skills/osdi-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "osdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-process into .cursor/skills/osdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path OSDI-Skills/skills/osdi-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/OSDI-Skills/skills/osdi-review-process .gemini/skills/osdi-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "osdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-process into .gemini/skills/osdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/OSDI-Skills/skills/osdi-review-process .github/skills/osdi-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "osdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-process into .github/skills/osdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/OSDI-Skills/skills/osdi-review-process .opencode/skills/osdi-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "osdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-review-process into .opencode/skills/osdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
osdi-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 807 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance…
- Reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period
- SKILL.md covers The pipeline, author's-eye view, What "no response period"…, Conditional acceptance and… and Structural facts worth knowing, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Conditional acceptance with heavyweight shepherding
What it does
Osdi Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance with heavyweight shepherding, co-chair recusal, notification timing, and the Jay Lepreau Best Paper lineage.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period
- Conditional acceptance with heavyweight shepherding
- Co-chair recusal
- Notification timing
Example prompts
- “/osdi-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Osdi Review Process loads about 1.7k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 807 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 807 words, ~1,744 tokens.
Download SKILL.mdSave it as
.claude/skills/osdi-review-process/SKILL.md (or your agent's skills folder).- name
- osdi-review-process
- description
- Use when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance with heavyweight shepherding, co-chair recusal, notification timing, and the Jay Lepreau Best Paper lineage.
OSDI Review Process
Model the pipeline the paper enters at the December deadline. The process facts below are the OSDI '26 cycle (verified 2026-07-08); OSDI re-decides its process per edition — '26 itself removed the response period — so read the current CFP's process section before predicting anything.
The pipeline, author's-eye view
Dec 11 submission complete on HotCRP (osdi26.usenix.hotcrp.com)
| double-blind PC review, typically multi-round:
| early round -> low-scoring papers exit with fewer reviews
| later round(s) -> surviving papers gather more reviews
| online discussion + PC meeting
| (no author-response step existed in the '26 cycle)
Mar 26 notification: accept | conditional accept | reject
| conditional: shepherd assigned, mandated-change list issued
Jun 9 shepherd-approved final paper due (or the acceptance lapses)
Jul 13 open-access proceedings live as the event opensRound structure and reviewer counts are PC-internal and vary; what is stable is the consequence: the first two or three pages decide whether the paper earns the later rounds, because early-round reviewers triage a large pile (capped at eight submissions per author, but multiplied across a big community).
What "no response period" changes about review
OSDI '26 eliminated the author response. Reading the decision process correctly means internalizing three shifts:
- Reviewer misunderstandings are terminal. A reviewer who misreads the threat
model or misses the baseline's tuning carries that reading into discussion
unchallenged. The only defense is prose that cannot be misread
(
osdi-writing-style's objection pass). - The PC discussion is where papers are saved or sunk — by other reviewers, not by you. A paper survives when its champion can answer objections from the paper's own text; write so a champion is armed.
- Conditional acceptance absorbs the dialogue. The conversation that a rebuttal would have hosted moves after the decision, into shepherding, where it has teeth: mandated changes, verified by a named shepherd, on a deadline.
Conditional acceptance and heavyweight shepherding
OSDI '26 stated the mechanism plainly: some papers are accepted conditionally, and will be rejected unless the authors make the changes the PC determined, completed by the final-paper deadline and approved by the shepherd. Treat it as:
| Property | Practical meaning |
|---|---|
| The change list is a contract | Scope it line by line; ambiguities are resolved with the shepherd, in writing, early |
| The shepherd is the gatekeeper | Their approval — not your opinion of completion — converts conditional to accepted |
| June 9 is the enforcement date | New experiments mandated in April need the frozen testbed from the review window (osdi-reproducibility) |
| It is not a negotiation to reopen | Relitigating the reviews with the shepherd burns the one relationship that can accept the paper |
osdi-author-response covers how to run the exchange itself.
Structural facts worth knowing
- Two tracks, one PC decision process: Research and Operational Systems papers are reviewed against different evidence expectations (novel design vs deployed experience) — know which bar your reviewers were told to apply.
- Co-chair recusal: OSDI '26 pre-committed that a submitting co-chair's papers are handled exclusively by the other co-chair under the same double-blind procedure — an unusually explicit conflict rule worth citing if conflict questions arise.
- Best-paper lineage: the Jay Lepreau Best Paper Award (inaugurated at OSDI '08) is selected by the PC from the accepted program; strong artifacts and clean claims correlate with it, but it is not something authors apply for.
- Openness after decision: accepted papers become free PDFs the day the event opens (USENIX open access) — reviews themselves stay confidential; OSDI does not publish reviews or decisions OpenReview-style.
Show full SKILL.md (320 more words)Show less
Surviving the triage round
Multi-round PC review means the paper's first job is to not exit early. What early-round reviewers can actually evaluate in a large pile:
- Pages 1–2 carry the whole argument — pain, gap, named idea, headline evidence with its cost. A reviewer who stops at page 3 should already be wrong to reject.
- The evaluation's table of contents — skimmers check that the strongest baseline appears and that a cost/limitations discussion exists before reading any numbers; their absence is a triage-round exit.
- Figure captions as a parallel paper — early readers walk the figures; captions that state takeaways ("recovery flat from 8 to 64 nodes; baselines linear") let the skim reach the right conclusion.
- Formatting smells — cramped spacing, page-13 spillover, or an appendix where
none is allowed mark the paper as careless before content is weighed
(
osdi-submission).
None of this is gaming; it is writing for the process that actually exists — one with early exits and no author response to recover from a bad first impression.
Reading a rejection usefully
Without a response phase, OSDI reviews are the only signal you get, so mine them:
recurring phrases across reviewers ("unclear workload realism," "incremental over X")
are the PC-meeting summary leaking through. Sort objections into fixable-by-writing,
fixable-by-experiment, and fit-level; the first two feed a SOSP/NSDI retarget within
months (osdi-workflow), the third sends you to osdi-topic-selection before any
retarget.
Decoding the decision letter
Three outcomes, three very different next moves: a clean accept still usually assigns a shepherd for lighter-touch final-version guidance — treat their suggestions seriously even when not framed as mandates; a conditional accept is a contract with a June enforcement date, decoded in the section above; a reject with substantive, convergent reviews is the system working — the reviews are the retarget's requirements document — while a reject with thin, scattered reviews usually means a triage-round exit, and the fix is the paper's first two pages, not its technical core.
Output format
[Phase] pre-decision / conditional / accepted / rejected
[Process facts confirmed live] response period? tracks? shepherding wording? (待核实 if unread)
[If pre-decision] top 3 misreadings the text invites (terminal without rebuttal)
[If conditional] change-list scoped? shepherd contact opened? June feasibility
[If rejected] objection triage: writing / experiment / fit + retarget call© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in OSDI-Skills/skills/osdi-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Osdi Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Osdi Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Review Pending PR Reviewsnrwl/nx | 29k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Reviewthedaviddias/Front-End-Checklist | 74k | — | ~556 | Automated safety check: Pass | MIT | |
| ReviewClickHouse/ClickHouse | 50k | — | ~8k | Automated safety check: Notes | Apache-2.0 | |
| Docling Pull Request Reviewdocling-project/docling | 69k | — | ~1k | Automated safety check: Pass | MIT | |
| Pre-Landing PR Reviewgarrytan/gstack | 136k | — | ~20k | Automated safety check: Notes | MIT |
Similar skills
Review
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews.
Review
ClickHouse/ClickHouse
Review a ClickHouse Pull Request for correctness, safety, performance, and compliance.
Docling Pull Request Review
docling-project/docling
Reviews or re-reviews a Docling pull request in fixed stages, with findings that can be reproduced and an explicit record of every check that was run.
Pre-Landing PR Review
garrytan/gstack
Reviews your diff against the base branch before merge, looking for SQL safety problems, LLM trust boundary violations, conditional side effects and other structural issues.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Osdi Review Process
What does Osdi Review Process do?
A skill your agent uses when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance…. Osdi Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance with heavyweight shepherding, co-chair recusal, notification timing, and the Jay Lepreau Best Paper lineage.
When should I use Osdi Review Process?
Osdi Review Process fits situations like: reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period; conditional acceptance with heavyweight shepherding; co-chair recusal; notification timing.
How do I install Osdi Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Osdi Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-review-process in your project. Codex loads it when a task matches its description.
Can I use Osdi Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/osdi-review-process, .gemini/skills/osdi-review-process, .github/skills/osdi-review-process and .opencode/skills/osdi-review-process in your project.
What does Osdi Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Osdi Review Process is instructions for the agent only.
Does Osdi Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Osdi Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Osdi Review Process use?
Osdi Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Osdi Review Process use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Osdi Review Process?
Skills that share tags, products or a category with Osdi Review Process: Review Pending PR Reviews (nrwl/nx, 29k stars), Review (thedaviddias/Front-End-Checklist, 74k stars), Review (ClickHouse/ClickHouse, 50k stars) and Docling Pull Request Review (docling-project/docling, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Osdi Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.