I got tired of PRs that just said "fix" — so I built a GitHub App that writes the description for you

We've all seen it. You open a pull request from a teammate — or your past self — and the description says: "fix bug" That's it. No context. No what changed. No why. You're now a code archaeologist trying to reverse-engineer intent from a diff. I've been that person. I've also been on the reviewing end, nudging people repeatedly for context that should've been in the description from the start. It's death by a thousand tiny frustrations. The real problem isn't laziness Developers don't skip PR descriptions because they don't care. They skip them because by the time the code is done, switching context to write documentation feels like starting a second job. You've been deep in the problem for hours. Writing "what changed and why" in plain English requires a different gear entirely. So most people don't. Or they write something just good enough to pass review, which ends up useless to anyone reading it six months later. What I built I'm a solo developer in Kerala, India, building PRDraft