Audits a project code THROUGH its Pipeline/ doc — reads a pipeline .md and its code together, then hunts for genuine bugs (correctness, sign/normalization, convention violations) and concrete optimizations (redundant recomputation, missing memoization, complexity blow-ups). Use to review a documented code for…
Runs when the agent finishes a response, executing promise-checker.sh and reap-wolfram.sh via bash (2 commands). From Mexregkan/claude-for-researchers.
★not rated 52
changed 1mo agoA
tokens not measured
originalMIT
The write-side inverse of /check-pipeline and the pipeline-auditor — read a Pipeline/ doc (and/or an audit report) and EDIT the code accordingly: apply an optimization the pipeline describes, correct code the pipeline (backed by your authoritative notes) shows is wrong, or bring the code in line with the documented…
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…
Format a result, derivation, or numerical value for independent verification by a second model. Use when you want a cross-check on an important or contested result.
Compile a LaTeX document and fix every error plus aesthetic issue (overfull/underfull boxes, widows, alignment, fonts) for a clean PDF and log. Use this instead of running pdflatex/latexmk manually — it avoids the latexmk stale-log trap and silent grep failures on binary log output, and it reformats rather than…
Convert Mathematica .nb or .m files to Wolfbook .wb format so they open and run in VS Code. Use when bringing existing .nb/.m files into Wolfbook, or to make an existing .wb bridge-safe.
Sync a local git clone of a shared Overleaf project: pull collaborators' latest, check whether Overleaf has moved ahead, or (only on explicit request) publish your local edits back — without ever erasing collaborators' work.
Re-derive a contested or pushed-back claim in isolation from the definitions, to catch sycophantic capitulation. Use when a result is disputed or you suspect you changed an answer only because the user pushed back.
Playbook for the Wolfbook MCP tools — driving the LIVE Wolfram kernel and a .wb/.nb notebook in VS Code from Claude Code (read/search/edit/run cells, evaluate expressions, checkpoint/restore kernel state, step-debug, look up symbols, find paclets, search INSPIRE/arXiv papers). Use whenever working through the Wolfbook…
Run heavy Wolfram Language (wolframscript) computations from Claude Code reliably, and diagnose the misleading "The product exited because of a license error". Use whenever invoking wolframscript on a non-trivial computation, when a wolframscript job dies with a "license error" despite a valid license, or when Wolfram…
Write (or refresh) a Pipeline/ .md that documents the calculation-and-code pipeline of ANY large code in the project — a notebook (.wb/.nb/.ipynb), an engine, or a script. Use when a load-bearing code has no pipeline doc yet, when a new main code is added, or when the user asks to "write the pipeline" for a file.…
Adversarially audits a result against the artifacts that produced it — a script, a log, a data file — and reports the WEAKEST statement those artifacts support. Spawn it with the artifacts and the drafted claim and NOTHING ELSE: no session history, no reasoning, no hoped-for conclusion. Use before a result leaves the…
Read-only fresh-context adversary for ONE claim of a project document. Given only the bare claim, its location and the evidence paths — never the caller's verdict — it reads the passage, the cited script / log / output and the sibling records, and returns the weakest statement the evidence supports, ranked breaks…
Read-only first pass over ONE section or line range of a project document (workbook section, strategy map, big picture, handoff, paper, primer) that extracts every checkable claim into ledger rows — id, location, falsifiable statement, type as written, load class, proposed check — and deliberately produces NO…
Commits and pushes for this project. Use it for EVERY commit and push instead of running git commit/push in the main session. Give it an explicit file list, the target repo, and the commit message. It enforces this project's git rules (no blanket staging, no trailers, protected files, push order) and reports the…
Decides whether the last round of work actually advanced the project, and specifies the single next task if it did not. Detects loops — the same residual renamed, a weaker check repeated, an escalation after a failed simple case. Spawn it with the last round's result, the audit of that result, and enough recent…
Audit what a passing script actually established, before writing any prose about it — build the computed-object ledger, rewrite every check's label as the weakest statement that makes its body pass, and separate the verdict on someone else's work from your own new claim. Run after the script passes and BEFORE the…
Evaluate one project document in detail — a workbook section, big picture, strategy map, handoff message, paper, brief, or primer — without editing it. Runs the mechanical lint, builds a claim ledger, types every headline against the eight claim statuses in CLAUDE.md, traces cited evidence to the scripts and logs that…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: