PR Conflict Flagger

Ops Based on this tweet by @ericzakariasson

The prompt

Set up a new bot for me on our busy repo. Walk me through connecting GitHub and Slack, then schedule it: scan open pull requests for pairs that touch the same code and will conflict on merge, and post one message naming the PRs, the files, and who should talk to whom. Ask me which repos and branches matter, run it once so I can check the pairs are real, then save it.

Paste it into Grok Bot, Rakazo or any agent you already use. It asks for what it needs, then saves itself as a bot.

Connect first

GitHubSlack

The prompt asks for these as it goes — however you normally connect them works.

Tired of signing in to each service for every harness? Executor signs you in once — every client shares the credentials. Try Executor → Sponsored

Run PR Conflict Flagger yourself

Free to copy, adapt, and edit after setup.

View source
Sponsored advertise →