Menu
Phase 4 — Run multi-model severity voting on confirmed issues. Writes votes.json next to each issue (append-only).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Phase 6 — Generate the REVIEW.md report by walking the append-only review tree. Optionally create GitHub Issues.
Add a custom issue spotter for the paper review. Describe what to look for and this will create the spotter file.
Phase 1 — Run the chunks x issue_spotters cross-product to find candidate issues. Uses edsl for parallel LLM review.
Phase 3 — Deduplicate confirmed issues by writing a dedup.json mapping file. No files are moved or modified.
Draft author responses for each confirmed issue. Writes response.json next to each issue (append-only).
One-shot holistic referee review of the full paper. Issues are written to .review/holistic/ as append-only issue.json files.
| name | vote-severity |
| description | Phase 4 — Run multi-model severity voting on confirmed issues. Writes votes.json next to each issue (append-only). |
| user-invocable | true |
| allowed-tools | Bash, Read, Write, Edit, Glob |
Run from the repo root. Requires investigated and deduplicated issues from Phases 2-3.
Look for the roboree scripts path in the system prompt (it will say "roboree scripts are at: "). Use that path:
python <r2-scripts-path>/vote_severity.py \
--review-dir .review/ \
--config .review/config.json
The script:
dedup.json if present)votes.json (resumable)votes.json next to each issue.json.review/severity.json summaryPer-issue — votes.json written next to issue.json:
{
"votes": [
{"model": "claude-sonnet-4-6", "severity": "major", "reasoning": "..."},
{"model": "gpt-4o", "severity": "major", "reasoning": "..."},
{"model": "gemini-2.5-pro", "severity": "moderate", "reasoning": "..."}
],
"consensus": "major",
"agreement": 0.67,
"voted_at": "<ISO timestamp>"
}
Top-level — .review/severity.json:
{
"issues": {
"chunks/model-00-a3f2/undefined_symbols": {"severity": "major", "agreement": 0.67}
},
"summary": {"major": 3, "moderate": 5, "minor": 2},
"voted_not_an_issue": ["chunks/intro-00-b7c1/logical_gaps"],
"created_at": "<ISO timestamp>"
}
Issues voted not_an_issue are NOT moved or deleted — they simply have a votes.json with "consensus": "not_an_issue" and are listed in the voted_not_an_issue array.
git add -A
git commit -m "review: severity voting — <M> major, <Mo> moderate, <Mi> minor"
Report: breakdown by severity, any issues rejected as not_an_issue.