Title-driven review makes a pull request understandable before the reviewer opens its description. A strong title distills the change, establishes the right review mindset, and reduces questions that create cognitive overhead. section 2.3.1
From vague to useful
“bug fix for invoice issue” identifies only a broad category and leaves urgency, scope, and the exact problem unclear. A reviewer may need to search for context before knowing what to examine. The description and tags can add the why, but they should remain optional for basic understanding. section 2.3.1
Use titles that:
- State the change in a concise, self-explanatory line. section 2.3.1
- Reserve descriptions and tags for additional context, especially the reason behind the change. section 2.3.1
