What problem does it solve? Most pull request descriptions merely restate the diff, forcing reviewers to reverse-engineer intent and leaving future readers of git log without context. This Skill produces PR titles and bodies that teach the reader the problem, the mechanism, the assumptions, and the evidence behind a change. ## Core Features & Use Cases - Essay-style PR writing: Structures descriptions as problem first, mechanism second, risks third, and omitted scope last, modeled on Andrew Clark and Sebastian Markbåge's PRs on facebook/react. - Repo-aware conventions: Reads the full branch (git log main..HEAD, git diff main...HEAD), checks PR templates and project rules, and matches existing title and squash-merge commit conventions. - Evidence-based test plans: Ends with a Test plan checklist carrying re-runnable evidence such as exact commands, before/after timings, and byte-identical output comparisons. - Use Case: After finishing a feature branch, ask for a PR description and get a title following repo conventions plus a body that explains the motivation, defines key terms, states assumptions and decision rules for uncertain bets, and lists verifiable test evidence. ## Quick Start Write a pull request title and description for my current branch compared to main, following this repo's conventions.
