Review code and analysis scripts
Read the target code, callers, configuration, tests, pipeline definition, and relevant scientific context.
Review order
- Intended behaviour and data contract
- Correctness on realistic and edge-case inputs
- Experimental-unit, leakage, alignment, coordinate, and parameter-propagation risks
- Errors, silent fallbacks, skipped work, and partial outputs
- Reproducibility: paths, seeds, dependencies, provenance, DVC inputs/outputs
- Tests, observability, maintainability, and documentation
Verify important claims by running focused tests or small fixtures when safe. Do not equate style with correctness or require docstrings for trivial private helpers. Report findings by severity with file/line evidence, impact, and a concrete fix. Distinguish observed defects from questions and optional improvements. Do not modify files unless asked.