Context/justification explains why a code change was made. It gives reviewers the decisions, circumstances, conversations, alternatives, and steps behind the implementation, reducing confusion during review. section 2.3.2
A useful justification can answer:
- Why was this implementation chosen? section 2.3.2
- Why was an apparently more obvious alternative rejected? section 2.3.2
- Which conversations, decisions, and steps shaped the change? section 2.3.2
A reviewable explanation
Use a few organized sentences or paragraphs to describe the situation, the chosen approach, rejected alternatives, relevant discussions, and the path taken to reach the change. Add a self-contained use case, such as a customer issue, open-ticket behavior, or happy path, when a scenario makes the rationale clearer. section 2.3.2
