ornlneutronimaging

Detection-only two-LLM-family review of the current branch's diff vs next (or a named branch/scope). Runs Claude + Codex finders through the dual-family-review engine, cross-family verifies P0/P1 findings, and reports at a human gate. Use to review a PR/branch before pushing or merging. Never edits, commits, or pushes.

Cut a NeuNorm release — pre-flight checks, promote next->qa->main, tag the version, watch the publish pipeline, and verify published artifacts. Use when shipping a new NeuNorm version to PyPI + conda.

Hunt for bugs in NeuNorm's src/neunorm using parallel Claude auditors plus, when installed, an independent Codex review, then consolidate verified findings. Use before a release or when reviewing risky changes.

Post-merge integration gate for NeuNorm — clean rebuild, full test run, and housekeeping (close addressed issues, update the task tracker / memory) after a PR lands on next. Use right after merging a PR.

Post-merge integration gate — cleanup, build, test, verify issues, update memory

Multi-stage iterative review pipeline across all active worktree branches

Post-merge integration gate — cleanup, build, test, verify issues, update memory

Multi-stage iterative review pipeline across all active worktree branches

Cut and publish a bm3dornl release — version bump, changelog, validate, promote next→qa→main, tag, and verify the publish landed

Cut a new iBeatles release — verify the promoted commit, create and push a v<X.Y.Z> tag, and confirm publish.yaml shipped conda (neutronimaging channel), PyPI (trusted publishing), and the GitHub release. iBeatles versions are tag-derived via versioningit, so there are NO version files to bump. Use when asked to "release", "cut a release", "tag a release", or "publish iBeatles".