[Maxion]

Jira issue generator.

Custom GPT with instructions that outputs issues according to our issue templates in markdown.

Allows me to write horribly typoed bullet point lists and get out surprisingly good issues.

Gets me 80-90% done in a fraction of the time. I can then just edit them to get them to be what I need.

What I'd really want to get working is a PR desription generator.

[matsemann]

Why can't the bullet points just be used as is? Either they contain enough signal, or they don't and llm won't help anyways.

I fear everything will be expanded by llms soon. "write an email, three paragraphs, about X", instead of just sending X directly. Then the receiver gets a wall of text, and uses an llm to distill it back to X' before reading. Just hope too much didn't get lost in the inverse compression through llm.

[Maxion]

> Why can't the bullet points just be used as is? Either they contain enough signal, or they don't and llm won't help anyways.

Because it is a lot messier and harder to understand when it's not structured. Having clearly structured tickets lessens the cognitive load.

[IanCal]

Short is not the same as clear and concise.

[kelvie]

I use copilot in emacs, and running "git commit -v" puts the diff in my emacs(client) buffer with copilot on and it's not terrible at describing the changes.

A lot of times it'll even guess the JIRA ticket number from the diff or the branch name.

[fl0id]

Gitbutler is doing that iirc and replit also might have sth like that

[videlov]

Currently GitButler only generates commit messages in this way (with some config options for style e.g. semantic commits). With that said, generating PR descriptions is something I was tinkering with this morning.

(disclaimer: I'm a GitButler co-founder)