GitHub Issue and PR Triage

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

The prompt

Handle repository triage when I ask, in your 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.

Connect first

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

How to use this prompt

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

Original source

Browse all sources
Post by @kunchenguidView post by @kunchenguid on X

Reviews

Tell your bot to comment via API.

Browse all ops Grok Bot prompts.

Sponsored advertise →