Peer Review Template
Structures a peer review of someone's analysis into must-fix, should-fix, and optional feedback instead of a vague "looks good."
Overview
Peer Review Template runs before any analysis that will influence a significant decision gets delivered: dashboards going to production, reports used for strategic decisions, A/B test conclusions, or anything cited externally.
What it covers
- Agrees the scope of review upfront: logic check, statistical validity, code review, or presentation clarity.
- Reviews analytical rigor: whether the question and method align, assumptions are valid, and the conclusion is supported by the data.
- Reviews code or SQL for reproducibility, correctness, readability, and performance when the analysis involves code.
- Writes specific, categorized feedback: must-fix issues, should-fix suggestions, and optional improvements.
- Tracks the author's response to each point and records a final sign-off once must-fix items are resolved.
Part of Data Analytics Skills
This is one of 31 skills in the Data Analytics Skills library, in the Workflow Optimization group.
Installation
- Clone the repo once:
git clone https://github.com/nimrodfisher/data-analytics-skills.git - Copy just this skill:
cp -r data-analytics-skills/06-workflow-optimization/peer-review-template ~/.claude/skills/(or~/.agents/skills/for Codex) - Ask your agent something like "review this teammate's analysis before it ships" and it activates on its own.
See the Data Analytics Skills entry for the full library.
Related assets
Frontend Design
Generates distinctive, production-grade UI that avoids generic "AI slop," with bold typography, cohesive color, and precise motion, implemented as real code.
Graphify
Turns a codebase, plus its docs, PDFs, images, and video, into a queryable knowledge graph that a coding agent can traverse instead of grepping raw files, and never guesses silently: every edge is tagged EXTRACTED, INFERRED, or AMBIGUOUS so you know what was found versus inferred.
Caveman
Makes your coding agent answer in a stripped down, high signal style that keeps every technical fact and cuts filler, saving output tokens on chat style questions.