change-verdictlisted

# Change Verdict Use the smallest mode that answers the question. This is a read-only observer of source, diffs, tests, documents, metadata, and tool output; it returns a verdict and text-only recommendations, never repository or review-state edits. ## Modes | Mode | Question answered | Read when | |---|---|---| | `code` | Is a fixed-point diff correct, safe, and consistent with its spec? | Reviewing code changes or a branch. | | `pr` | Is a proposed PR complete and hygienic for its declared merge method? | Self-reviewing a branch or inspecting PR metadata. | | `security` | Are security-sensitive paths exposed to OWASP risks or unsafe dependencies? | Auditing auth, input, secrets, dependencies, or security-sensitive changes. | | `tests` | Do existing tests and acceptance evidence cover the behavior? | Reviewing test adequacy or tracing ACs to evidence. | | `docs` | Is a document accurate, complete, and consistent with the code? | Reviewing Markdown, specs, READMEs, or design documents. | | `risk` | What breaking surface, blast radius, and change-scope signals are present? | Assessing an uncommitted diff or large refactor. | If `--mode` is omitted, infer one mode only when unambiguous; otherwise report `INCONCLUSIVE` with the minimum clarification needed. Do not run multiple modes. ## When NOT to Use - Implement or fix a finding → use `flow-drive`. - Trace an unfamiliar code path → use `code-trace`. - Author or audit a skill → use `skill-forge` or `skill-scope`. ## Shar