Issue

Output language: answer and write artifacts in the user's own language (match their messages, not the repo's history).

Overview

Turn a sentence into a filed, trackable issue: identify the host → pick a template → compose the draft and title → search for duplicates → resolve labels → confirm → write → report. A duplicate hit routes to updating that issue instead of filing a new one.

This skill files and updates issues. It does not fix them, branch for them, or open PRs for them.

Each stage has its own reference — this file is a router:

Stage	What	Reference
Templates	host identification, the three tiers, repo-local-first resolution, the optional copy-in step	references/templates.md
Create	draft + title → dedupe → labels → confirm → create → report; every failure path	references/create.md
Host CLI	the measured `gh` / `glab` commands and the traps	references/host-cli.md

Copy-in candidates live in assets/: bug-report.md · feature-request.md · custom.md.