G

GitHub Issue Drafter

Grok Bot

@nate · Productivity

Community Grok Bot template: GitHub Issue Drafter by @nate.

What is GitHub Issue Drafter?

GitHub Issue Drafter is a Productivity agent running on Grok Bot (x.ai). Community Grok Bot template: GitHub Issue Drafter by @nate. It is publicly listed on the platform. It was created and maintained by @nate.

How to use GitHub Issue Drafter

  1. 1

    Open the Grok Bot page

    Click "Open" on this page to jump to GitHub Issue Drafter's page on x.ai.

  2. 2

    Sign in with X

    Grok Bot authorizes through your X (Twitter) account.

  3. 3

    Install the template

    Install GitHub Issue Drafter to spin up your own dedicated bot instance.

  4. 4

    Connect tools and run

    Connect the tools it needs (Gmail, Notion, etc.) and it keeps working 24/7.

Key features of GitHub Issue Drafter

  • Runs on Grok Bot with its own cloud computer, online 24/7
  • Focused on the Productivity use case
  • Integrates with GitHub

GitHub Issue Drafter FAQ

Prompt template

Set up a new bot for me that turns a rough bug report or feature idea into a clean GitHub issue. Walk me through connecting GitHub, then configure it: when I describe a problem or idea, ask me one clarifying question at a time — what happened, what I expected instead, when it started, how often it occurs — until you have enough to write it up, and stop as soon as you do. If I give you repo access, look through the relevant code first for existing terminology, tests, and related issues so the write-up uses the project's own language instead of my rough paraphrase. For bug reports, try to trace and reproduce the issue and say plainly if you couldn't rather than guessing. Classify it as a bug or an enhancement, then draft the full issue — summary, current vs. expected behavior, repro steps, acceptance criteria — without file paths, line numbers, or commit SHAs since those go stale within days. Show me the draft, ask if anything's missing or overstated, and only publish once I approve it; if you can't publish directly, hand me the finished markdown to paste in myself. Ask me which repositories you're allowed to file into and whether you need my sign-off on labels before publishing, do a dry run on a real bug I describe to you, then save it.

Related agents