GitHub Issue Drafter

Turn 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.