What problem does it solve? Reviewing a release component's diff across multiple expert lenses and tracking the resulting findings is hard to coordinate when review state lives in repo-local files that differ across machines, people, and agents. This Skill runs the configured change lenses against a component's diff and records findings durably in the shared Marshall store, so one person's review is visible to everyone working the release. ## Core Features & Use Cases - Multi-lens diff review: Loads the configured change lenses from the store, pre-filters them against the component's changed files with lenses_applicable, and fans out one subagent per applicable lens. - Store-backed findings: Reconciles fresh findings against existing kind: "change" findings and records the whole pass in one atomic record_findings call, with defer/accept/fix/re-open handled via resolve_finding. - Component scoping with fail-loud resolution: Resolves the component from an explicit ref, the active claim, or the branch name, and stops on any disagreement rather than mis-scoping findings. - Use Case: A developer finishes a backend component on a release branch and asks for a change review; the Skill fetches the diff against the default branch, runs only the lenses applicable to those files, and records findings visible to the whole release team. ## Quick Start Ask the assistant to run a change review on the current component of your Marshall-tracked release, for example by saying "review this component" or invoking /marshall:change-review with a component ref.
