What problem does it solve?
Pull request titles and descriptions often bury the actual change under context, restate the diff, or use jargon that reviewers cannot parse, making code review slower and the commit history less useful. This Skill evaluates PR prose against readability principles and produces concrete proposed rewrites.
Core Features & Use Cases
- Readability Evaluation: Checks whether the title stands alone, the description leads with the change and its purpose, and non-obvious decisions explain the why.
- Concrete Rewrites: Produces findings paired with specific proposed rewrites for the title and description, without applying them automatically.
- Light Format Check: Secondarily confirms the title follows the
[type] Description pattern within ~63 characters and required template sections are present.
- Use Case: Before requesting review on a PR, run this Skill to catch vague titles like "[fix] Fix the bug" and descriptions that narrate the diff instead of explaining intent.
Quick Start
Review the title and description of PR number 123 for readability and suggest improved wording.