check-pipeline

# /check-pipeline — verify a code matches its pipeline doc Pipeline docs drift when the code changes: a function gets renamed, a cell is inserted (shifting all later cell numbers), a data file is dropped, an I/O contract changes. This skill compares a `Pipeline/*.md` against the current source and reports every mismatch, so the map stays trustworthy. ## When to use - Right after editing a documented code. - Before relying on a pipeline doc you didn't just write. - On request: "is the pipeline still accurate?", "check the codes match the pipelines". - Across the board (no argument): check every `Pipeline/*.md` against its code. ## Method **1. Pair each pipeline doc with its code.** The doc's header names it ("Code: path/to/<file>"). Read the header, or scan the folder if checking everything. **2. Dump the code** to readable text (same helper the writer uses): ```bash python3 .claude/skills/write-pipeline/dump_code.py "$SCRATCH" "path/to/<file>" ``` **3. Extract the doc's checkable claims and verify each against the dump:** - **Symbols** (every name in the "Key symbols" table and in prose code-spans): does it still appear in the code? `grep -F 'symbolName'` the `.full.txt` (or source). Flag any that are **absent** (renamed/removed) — the highest-value drift signal. - **Cell numbers**: for each `| Symbol | Cell N |` row, confirm the symbol's definition is at/near cell N in `<base>.outline.txt` (±2 tolerates minor insertions; larger shifts = flag "cell numbers stale...