review-notebook

Review Jupyter notebooks for leakage, statistical missteps, and reproducibility issues.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/tim-krausz/mlstack --skill review-notebook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-notebook
Source: https://github.com/tim-krausz/mlstack/tree/main/review-notebook
Command: npx skills add https://github.com/tim-krausz/mlstack --skill review-notebook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams conduct rigorous, pre-submission notebook reviews to identify methodological flaws, leakage, and narrative gaps, ensuring reproducibility and trust in results.

Core Features & Use Cases

  • CRITICAL review workflow: Systematically assess data leakage, statistical validity, and reproducibility across notebooks.
  • Two-pass guidance: Distinguish critical methodological risks from informational quality improvements.
  • Result-oriented outputs: Generate actionable recommendations and improvement notes for notebook authors.

Quick Start

Review notebooks in the repository with the /review-notebook workflow and follow the steps in the checklist.

Frequently Asked Questions about review-notebook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a Jupyter notebook for data leakage and statistical validity issues?

You can review notebooks for data leakage and statistical validity by running a structured two-pass assessment workflow that identifies methodological missteps, flags p-hacking risks, and generates actionable remediation notes for authors.

What is notebook reproducibility review and when do I need it?

Notebook reproducibility review is a pre-submission audit validating analyses for methodological flaws, data leakage, and statistical missteps. You need it when finalizing data science workflows to ensure results are trustworthy and reproducible.

How do I review a notebook for p-hacking and reproducibility issues step by step?

Review a notebook for p-hacking and reproducibility by applying a two-pass assessment: the first pass isolates critical methodological risks like data leakage, and the second generates structured, actionable improvement recommendations for the author.

Can I use this notebook review workflow for data science projects from drafting to final submission?

Yes, this notebook review workflow applies to Jupyter notebooks across data science workflows, enabling reviewers to audit methodological quality continuously from early drafting stages through to final submission.

What is the best way to audit methodological quality in data science notebooks?

The best way to audit methodological quality in data science notebooks is a two-pass review workflow that distinguishes critical methodological risks from informational improvements, providing structured outputs for actionable remediation.

Why does my notebook analysis fail reproducibility checks before submission?

Your notebook analysis may fail reproducibility checks due to undetected data leakage, statistical missteps like p-hacking, or narrative gaps. A systematic review workflow identifies these methodological flaws and guides remediation.