Individual skill
reviewing-code-for-science
Reviewing scientific code — correctness, reproducibility, numerical soundness, and constructive feedback.
skills/reviewing-code-for-science/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
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 8, 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.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- research Derived category
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 · 6,675 bytes
Read excerpt
## Overview
Scientific code review differs from software code review: the primary
question is whether the code correctly implements the science, not
whether it follows style guides. This skill covers reviewing for
correctness (algorithms, units, edge cases), reproducibility
(environments, seeds, versions), numerical soundness, and giving
feedback that improves both the code and the science it produces.
## When to use
- Reviewing code accompanying a manuscript or in a pull request
- Auditing a collaborator's analysis pipeline before trusting its output
- Checking reproducibility of published computational results