Change Traceability Review

Review the traceability behind a change, not code style: Story or issue -> Spec -> plan/tasks -> commit/branch/PR -> diff -> tests -> risk. Default to Chinese and keep the report compact and decision-oriented. Treat specs as the review source of truth; code is acceptable when it clearly serves the spec.

Modes

• Spec Preparation: before implementation or commit, create or tighten a Story-linked spec and define acceptance scenarios, plan/tasks, tests, and risk evidence that later commits can cite. Load Spec Contract.
• Review Readiness Check: inspect the current diff, staged diff, PR text, branch, or selected commits before review/merge. Load Mode Rules and Reporting.
• Review Retrospective: inspect recent history, usually latest 30 commits. Identify commit-message habits, weak traceability, missing Spec/Test/Risk evidence, oversized or mixed-scope commits, spec-doc patterns, and rework signals. Load Mode Rules and Reporting.