What problem does it solve? Pull requests often contain internal jargon, references to external documents, and convoluted sentences that only make sense to the author. This blocks first-time reviewers (new hires, other teams) from understanding the PR, causing review delays and endless question round-trips. ## Core Features & Use Cases - Context Check: Detects issue/PR-only labels (e.g., "Phase-2"), references to files or tickets the reviewer cannot open, undefined abbreviations, and implicit assumptions, then suggests replacing, self-containing, or deleting them. - Readability Check: Flags sentences that require a second read—multiple claims per sentence, distant subject-verb pairs, nominalization, roundabout predicates, buried conclusions—and rewrites them without changing meaning. - Use Case: Before submitting a PR, run the check across the title, body, commit messages, and code comments to produce a findings table with before/after fixes so any reviewer can understand it on first read. ## Quick Start Check my current pull request for jargon and readability issues that a first-time reviewer would stumble on, and fix them.