viv

Parallel multi-lens code review across maintainability, DRY, design, tests, documentation, and functional correctness.

Trace a simulation regression across vivarium repositories to identify the behavioral change causing it.

Use when: analyzing diffs between branches across one or more repos, summarizing code changes relevant to a regression, identifying which component changes could affect simulation outcomes.

Test a single hypothesis about the cause of a simulation regression by comparing old and new code.

Use when: reviewing code for design and data structure choices, algorithmic efficiency, whether the right abstractions are used, representation trade-offs, API surface design.

Use when: reviewing code for documentation quality, including docstrings, comments, README/changelog updates, and public API documentation accuracy.

Use when: reviewing code for DRY violations, duplicated logic, repeated patterns, opportunities to extract helpers or shared utilities, near-identical code blocks.

Use when the user asks about vivarium-suite CI — build status, Jenkins console logs, job structure, GitHub Actions runs, etc. Covers the GH Actions / Jenkins setup, the per-package Multibranch Pipeline layout, URL-to-jobFullName translation for the Jenkins MCP, and parallel matrix log interleaving.

Use when the user is performing post-install configuration for components shipped by this plugin — work that the plugin install itself doesn't perform.