Write an enthusiastic, well-structured PR description for the current changes. Use when the user is about to open a pull request and says "write a PR description", "describe these changes", or "hype up this PR".
npx @senso-ai/shipables install KeyanVakil/pr-hype-manTurn the current diff into a PR description that makes reviewers actually want to read it.
git diff main...HEAD (or equivalent base branch) to see all changes.git log main...HEAD --oneline to get the commit history.## What's this?
<1-2 sentences. The elevator pitch. What does this PR do and why does it exist?>
## Changes
<Bullet list of the meaningful changes. Group related ones. Skip trivial stuff like formatting.>
## Why this way?
<Optional. Only include if there were non-obvious architectural or approach decisions worth explaining.>
## How to test
<Concrete steps a reviewer can follow to verify this works. Not "run the tests" — actual user-facing verification steps.>
## Screenshots / Demo
<If UI changes exist, note that screenshots should be added. If no UI changes, omit this section.>