file-issue

# File a GitHub issue Turn a rough idea, bug report, or low-priority task into a **well-structured GitHub issue** and file it with `gh`. The output should be something an outside contributor can pick up cold — accurate file pointers, clear scope, explicit acceptance — not a one-line stub. ## Scope boundary (read first) Rove tracks its own work in the **daemon-owned issue store** (`rove api issue-*`, the web Issues page) — see [`docs/WORK-TRACKING.md`](../../../docs/WORK-TRACKING.md). That is the default for internal backlog. This skill is for **outward-facing GitHub issues** — work you intend to hand to external contributors (especially `good first issue`s), or a public bug report. If the user just wants to jot down internal backlog, prefer the daemon store and say so. If they explicitly want a GitHub issue, proceed here. ## Modes The skill handles three shapes of input — detect which from the user's ask: - **Single** — one idea / bug → one issue. Draft it, auto-classify (Step 1), confirm, file. The lightest path; fine to file directly once the draft + labels are shown. - **Batch** — a list of ideas / a backlog dump / "file these N as issues" → many issues. Draft all, classify each, present the whole set as a table (title + proposed labels) for **one** confirmation, then file them in a loop and report URLs together. - **From unsolved problems** — the user points at problems that came up but weren't fixed this session ("发没解决的上去") — e.g. a known bug you hit, a de...