What problem does it solve? Pull requests often contain context-dependent jargon (project-only labels like "Phase-2", references to files reviewers cannot open, undefined abbreviations) and hard-to-read sentences (long multi-claim sentences, nominalizations, buried conclusions) that block first-time reviewers from understanding the change without back-and-forth questions. ## Core Features & Use Cases - Context Dependency Detection: Flags issue/PR-only naming, unlinked external references, undefined abbreviations, implicit assumptions, and raw internal IDs that a new team member cannot resolve. - Readability Analysis: Identifies sentences with multiple claims, distant subject-verb pairs, nominalized verbs, roundabout predicates, and conclusions buried at the end, with concrete before/after rewrite patterns. - Full PR Coverage: Inspects the PR title, body, commit messages, diff comments, and newly introduced identifiers using gh pr view, gh pr diff, and git log. - Use Case: Before submitting a PR, run the check to confirm a reviewer from another team could understand it from the PR alone, then apply the suggested fixes and show before/after diffs. ## Quick Start Check whether my current pull request is understandable to a first-time reviewer and fix any jargon or hard-to-read sentences.
