Individual skill
research-review
Not available
skills/research-review/SKILL.md
Source commit 894598cd3a90891a077c254566276bd379038bad
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 251
- Repository last updated
- Oct 30, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,047 bytes
Read excerpt
# Claude Code Research Review Guide
This document outlines a comprehensive peer review workflow for ML research implementations, with three key phases:
## Core Review Process
**Initial Validation**: The workflow first checks prerequisites—ensuring `ml_res.md` exists (from implementation phase) alongside planning and survey documents. If missing, it halts with a clear directive: "需要先运行 /research-implement 完成代码实现" (complete implementation first).
**Atomic Concept Verification**: Rather than general code inspection, the review extracts "atomic academic concepts" from survey documents—individual formulas, loss functions, normalization layers. Each concept gets mapped to expected code locations, then verified line-by-line. A checklist table documents whether each concept is correctly implemented (✓), missing (✗), or oversimplified.
## Performance Assessment (New Standard)
The workflow now treats performance validation as mandatory, not optional. After 2-epoch validation, it calculates loss reduction percentage and compares metrics against random baselines. If loss decreases less than 5% or accuracy stays within ±10% of random chance, it flags "性能异常" (performance anomaly).
This triggers **Step 5b—Algorithm Reflection**: adjusting hyperparameters (learning rate, batch size, normalization) up to 2 iterations, with quantified before/after comparisons. Changes are restricted to training configuration; core algorithm logic remains protected.