GitHub Issue and PR Triage

Copy this complete Grok Bot prompt to create a ops workflow using GitHub. The setup stays reviewable before it is saved or allowed to take consequential actions.

Ops 0 copies Based on this post by @kunchenguid · scouted by @elie2222

The prompt

Set up a new bot for me I can trigger for repository triage, in its own dedicated chat. Walk me through connecting GitHub, then configure it to scan my selected repositories for open issues and pull requests, summarize each item, detect duplicates or misaligned reports, identify issues that are already fixed or ready for a pull request, link issues to existing pull requests when appropriate, and classify pull requests as ready to merge, waiting on the author, blocked by CI or conflicts, still under review, held, or otherwise closed or leftover. Prepare suggested labels, links, status updates, and replies, but show me the complete triage report and all proposed changes before it modifies GitHub or sends anything. Ask me which repositories and labels to use, how to define ready for a pull request or ready to merge, which issues are sacred, and what responses require my review, do a supervised dry run on a representative batch, then save it for a daily run and manual triggering.

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

GitHub

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

How to use this prompt

Copy the full prompt. Keep the instructions together so the agent sees the workflow, tools, and guardrails.
Paste it into your agent. Answer the setup questions and connect the required tool when asked.
Review the first run. Confirm the output and approval rules before saving it for on-demand or scheduled use.

Run GitHub Issue and PR Triage yourself

Free to copy, adapt, and edit after setup.

View source