verify-chapter

Re-runs chapter verification tests, fix loops, and parity checks for fluid mechanics notebooks.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/shammun/fluidpy --skill verify-chapter-shammun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-chapter
Source: https://github.com/shammun/fluidpy/tree/main/.claude/skills/verify-chapter
Command: npx skills add https://github.com/shammun/fluidpy --skill verify-chapter-shammun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a chapter's physics code or content changes, you need to re-validate correctness without rebuilding the whole chapter. This Skill re-runs only the verification phase—tests on the V1-V7 evidence ladder, benchmark references, and report generation—so regressions are caught quickly. ## Core Features & Use Cases - Targeted Re-Verification: Briefs the math-verifier on the chapter's evidence ladder tests proportional to curation tiers, then reports the verdict, per-label counts, and observed convergence orders. - Implementer Fix Loop: On FAIL, loops with the concept-implementer (max 3 iterations) applying physics-only fixes while keeping public signatures stable. - Post-Fix Consistency Checks: Re-runs explainer parity (tools/shot.py --quick) and notebook execution (tools/run_notebook.py) since physics changes may affect outputs, then updates progress.json and commits. - Use Case: After editing a chapter's solver, run /verify-chapter 7 to confirm all tests still pass, explainer screenshots still match, and the notebook still executes end-to-end. ## Quick Start Run /verify-chapter 7 to re-verify chapter 7's tests, fix any physics failures, and re-check explainer parity and notebook execution.

Frequently Asked Questions about verify-chapter

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

FAQPage Schema
How do I re-verify a chapter after changing its physics code?

Run /verify-chapter N with the chapter number. It re-executes the V1-V7 evidence ladder tests, loops with the implementer on failures (max 3 iterations), then re-checks explainer parity and notebook execution.

What does the verify-chapter skill check besides tests?

Beyond the test ladder, it runs tools/shot.py --quick for explainer selftest parity and tools/run_notebook.py to confirm the chapter notebook still executes, since physics changes can alter outputs.

What happens when chapter verification fails?

On FAIL, the skill loops with the concept-implementer up to three times, applying physics-only fixes while keeping public function signatures stable. If still failing, open items are reported.

Does verify-chapter modify public API signatures?

No. The fix loop is restricted to physics corrections only; public signatures must remain stable so notebooks, explainers, and downstream chapters keep working.

When should I run publish-chapter after verify-chapter?

If the chapter was already published and verification passes with changes, the skill suggests running /publish-chapter N so the updated notebook, explainers, and web pages are redeployed.