create-github-ticketlisted

# Skill: create-ticket Create or update a GitHub issue (feature request, bug report, or refactor task). ## IMPORTANT - Always use gh CLI to create or update tickets. Never call the GitHub API directly. - If gh CLI is not available, abort and ask the user to install it. The user must restart the skill then. - When any gh call fails, use AskUserQuestion to ask the user what to do (repeat, stop, do something else). ## Instructions ### Step 1 – Determine mode Inspect `$ARGUMENTS`: - If context contains `update` and/or an issue number or GitHub issue URL → **update mode**. - Otherwise → **create mode**. - If create mode does not make sense based on context, use AskUserQuestion. ### Step 2 – Gather information **Create mode:** - Extract issue type (`feature`, `bug`, `refactor`) from `$ARGUMENTS`; if missing, ask the user. - For `feature`: understand the desired behaviour and why it is needed. - For `bug`: understand current vs. expected behaviour and reproduction steps. - For `refactor`: understand scope, motivation, and target state. **Update mode:** - Fetch the issue: `gh issue view <number-or-url>`. ### Step 3 – Research (optional) If the issue involves a specific library, framework version, API, or configuration that you are not fully certain about, use AskUserQuestion to ask: *"Should I search online for [topic] to get accurate details before drafting?"* If yes, use `WebSearch` / `WebFetch` to collect relevant facts and incorporate them into the draft. Skip this