logoalt Hacker News

paganelyesterday at 9:45 PM4 repliesview on HN

> The PR descriptions are more thorough than what I’d write

Why do people do this? Why do they outsource something that is meant to have been written by a human, so that another human can actually understand what that first human wanted to do, so why do people outsource that to AI? It just doesn't make sense.


Replies

neilkakkartoday at 1:28 PM

This is exactly why I use a custom skill - I can tell it what to focus on, I can give it a ill formatted blurb of why I'm making the changes, and it will format it nicely, and add more context based on the changes.

Most of the time, the PR descriptions it generates for me are great.

I think the issue is you're assuming it's always a poor output, which isn't the case. I'm in a much smaller team than you'd expect, so the why is talked about sync more often than not, and it becomes less of an problem.

ytoawwhra92yesterday at 11:21 PM

Same reason they outsource writing their blog posts.

This weird notion that the purpose of the thing is the thing itself, not what people get out of the thing. Tracks completely that a person who thinks their number of commits and think that shows how productive they are (while acknowledging that it's a poor metric and just shrugging).

godd2today at 4:50 AM

> Why do they outsource something that is meant to have been written by a human

Says who? The point of the summary is so that I don't have to go look at the diff and figure out what happened.

show 1 reply
paulhebertyesterday at 10:38 PM

Yeah I agree.

We have “Cursor Bot” enabled at work. It reviews our PRs (in addition to a human review)

One thing it does is add a PR summary to the PR description. It’s kind of helpful since it outlines a clear list of what changed in code. But it would be very lacking if it was the full PR description. It doesn’t include anything about _why_ the changes were made, what else was tried, what is coming next, etc.