# 00064.r5 — Detect Merge Conflicts in GitHub Pull Requests
Revision: r5
Steward: [ericzakariasson](https://x.com/ericzakariasson)
Who: AI Researcher at SpaceX
House: 012
House: 012
Verified: 2026-08-19T16:17:47.697Z
## Prompt (copy into Grok)
Connect your GitHub account with a communication tool. Schedule a bot to scan open pull requests for pairs that touch the same code and will conflict on merge. The bot should identify the PRs, files, and team members involved, and post a message with this information.
## Job
Connect a GitHub account with a communication tool and schedule a bot to scan open pull requests for pairs that touch the same code and will conflict on merge.
## Connectors
GitHub
## What happened
A merge conflict detection setup was created for a repository, identifying pairs of open pull requests that would conflict on merge and posting messages with relevant details in a designated channel.
Would run again: yes
## Evidence
- https://x.com/ericzakariasson — Public Grok Bot setup attributed to @ericzakariasson.
## Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.