In general it is better to constrain the LLM into what you need BEFORE you let it do things, because bot runs are expensive. So you'd want to build that into your prompt somehow.

How would I describe this to a bot in a prompt?

PS: I saw something fun (but postvalidation, so it is still no bueno) this morning that may help with PR pre-review automation: an anti-slop linter. For example it has the nice rule no-known-value-widening, that would destroy you if you were to do:

function isUser(value: unknown): value is User {
  return UserSchema.safeParse(value).success;
}

declare const user: User;
isUser(user);

Which funnily, I ran into in my review of a library - about which I was complaining to k00b last week - where someone had a Fable-tagged commit refactoring their 50k line repo from javascript into typescript where all the types were any unless they were clearly a string or Buffer *cough*. I swear they must have one-shotted that entire refactor: /model fable-5.5-max Yo Claude convert my shit to typescript, tag a major version and push to GH. And then the CD pipeline will push your lib to npm after which 2 million dependents will use it. Especially because you push a vuln fix right after that.

I can't beat that kind of retardation. All I can do is jump out of a 15th floor window.