rvw-walkthroughlisted

# rvw Walkthrough management Create a first reading path that helps a reviewer build a mental model of a committed change or requested implementation subject and continue into the code. Treat the Walkthrough as orientation, not as the code's source of truth, an exhaustive change log, a completed AI review, a review-scope guarantee, or an approval plan. Follow explicit instructions from the user, caller, Pull Request body, or an upstream Skill before any default in this Skill. Instructions may set the reading order, focus, format, detail, scope, exclusions, assumed knowledge, design decisions to explain, or non-code evidence to include. Apply the default authoring guide only where those instructions are silent. Add only the minimum context needed to keep the requested Walkthrough understandable; never replace the requested purpose with a different one. Prefer verified repository and subject facts. Use the smallest necessary inference when facts do not establish intent, label the uncertainty, and never invent business requirements or off-repository constraints. Leave the document's organization, emphasis, granularity, step count, and use of diagrams to the current request and subject. Do not impose fixed headings or a narrative template. Use only the `rvw` CLI protocol. Never access the SQLite database directly or control a viewer through browser automation. ## Preflight 1. Run `rvw protocol --json` and parse stdout as JSON. 2. Require `protocolVersion` 4, `agent.transpo