Check that a code and its Pipeline/ .md are still compatible — that every symbol, cell number, data file, and data-flow claim in the pipeline doc still matches the current code (drift detection). Use after editing a documented notebook/engine/script, before trusting a pipeline doc, or on request ("does the pipeline still match the code?"). Reports mismatches (missing symbols, wrong cell numbers, renamed functions, changed I/O) and can update the doc. Companion to /write-pipeline.
$npx -y skills add mexregkan/claude-for-researchers --skill check-pipelineInstalls into the current project.
Run `npx skills use "https://github.com/mexregkan/claude-for-researchers" --skill "mexregkan/claude-for-researchers/check-pipeline"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/mexregkan/claude-for-researchers" that are relevant to the current task. Run `npx skills add "https://github.com/mexregkan/claude-for-researchers"` and select the relevant skills, then follow their instructions.