create-issuelisted

# Create Issue Goal: File a GitHub issue with a Conventional Commits prefixed title and a fixed English skeleton focused on **why** the work is worth doing. Follow-up sections (What / Acceptance / Plan) are intentionally deferred to the moment work actually starts, not filing time. This skill is **create-only**. Edits and closures are out of scope; use `gh issue edit` / `gh issue close` for those. ## Title format `<type>: <concise summary>` `<type>` is a Conventional Commits prefix: | prefix | when to use | | ---------- | ---------------------------------------------------------- | | `feat` | new user-facing capability | | `fix` | bug / incorrect behavior | | `refactor` | internal restructure, no behavior change | | `perf` | measurable performance improvement | | `chore` | maintenance, deps, tooling without behavior change | | `docs` | documentation only | | `test` | tests only | | `build` | build system, Dockerfile, packaging | | `ci` | CI config / pipelines | When two prefixes fit (e.g., Dockerfile optimization → `perf` vs `build`), pick by the **primary motivation**: `perf` if the goal is speed/size, `build` if it's reorgani