← ClaudeAtlas

notebook-ci-pipeline-authorlisted

Use when Jupyter notebooks must run in CI as tests, their outputs must stay stable, or a PR adding notebooks needs review. Wires papermill parameterized runs, nbval output checks, testbook unit tests, nbstripout and artifacts into GitHub Actions, plus a review checklist with a BLOCK or PASS verdict.
testland/qa-skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill testland/qa-skills
# notebook-ci-pipeline-author Composes the three notebook testing tools into one GitHub Actions pipeline: papermill executes parameterized notebooks, nbval validates output regression, testbook runs function-level unit tests, and nbstripout gates committed output. Per-tool depth lives in [references/papermill.md](references/papermill.md) (parameterized execution) and [references/nbval.md](references/nbval.md) (output regression); this SKILL.md covers the wiring and integration decisions, plus the PR review checklist for notebook changes. ## When to use Teams using all three tools but assembling the pipeline by hand: no consistent artifact naming, no shared caching, duplicate install steps, no HTML report on failure. Also: any PR that adds or modifies `.ipynb` files and needs the review checklist below. ## Hard-reject conditions Do not proceed if any of the following apply: - The repository has no `parameters`-tagged notebook cell. Papermill injection silently uses notebook defaults when the tag is absent per the [Papermill execute docs]; the pipeline will report green against stale values. - nbval ground-truth outputs are absent from the committed `.ipynb` files. Re-running cells with no stored outputs produces no diff, so regressions are invisible. - testbook tests use `execute=True` per-function without a `scope="module"` fixture. Each test re-executes the kernel; CI timeouts follow per the [testbook docs]. State the blocker to the user and stop. ## St