一键导入
investigate
Phase 2 — Investigate candidate issues. Writes investigation.json next to each issue.json with evidence and a confirm/reject verdict.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Phase 2 — Investigate candidate issues. Writes investigation.json next to each issue.json with evidence and a confirm/reject verdict.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 | investigate |
| description | Phase 2 — Investigate candidate issues. Writes investigation.json next to each issue.json with evidence and a confirm/reject verdict. |
| user-invocable | true |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep, Agent |
Run from the repo root. The paper source is in this same repo.
Read .review/config.json to find the paper commit SHA and manuscript path.
Scan for all issue.json files that do NOT yet have an investigation.json next to them:
.review/chunks/<chunk-id>/<spotter>/issue.json (from broad sweep)
.review/holistic/<slug>/issue.json (from holistic review)
Skip any directory that already has investigation.json (already investigated).
Use the investigate-issue sub-agent or investigate directly.
.review/config.json shows has_code: true).review/config.json shows has_data: true)Write investigation.json next to the issue.json (in the same directory). Never move or modify issue.json.
Confirmed:
{
"verdict": "confirmed",
"location": {"file": "<path>", "lines": [<start>, <end>]},
"category": "<category>",
"evidence": [
{"searched_for": "<terms>", "scope": "<where>", "found": "<what>"}
],
"suggested_fix": "<actionable suggestion>",
"models_flagged": ["<model>"],
"investigated_at": "<ISO timestamp>"
}
Rejected:
{
"verdict": "rejected",
"rejection_reason": "<concrete explanation with line numbers or code locations>",
"investigated_at": "<ISO timestamp>"
}
Uncertain:
{
"verdict": "uncertain",
"notes": "<what was checked, why it's unclear>",
"investigated_at": "<ISO timestamp>"
}
git add -A
git commit -m "review: investigation — <C> confirmed, <R> rejected, <U> uncertain"
Report: number confirmed, number rejected, brief summary of the most significant confirmed issues.