gh-create-issue

# GitHub Create Issue Use this skill when the user requests to create an issue. Must follow the repository's issue template format. ## Workflow ### Step 1: Determine Template Type Analyze the user's request to determine the issue type: - If the user describes a problem, error, crash, or something not working -> Bug Report - If the user requests a new feature, enhancement, or additional support -> Feature Request - If the user is asking a question or needs help with something -> Questions & Discussion - If the user describes engineering work with no user-facing behavior change (a follow-up deferred from a pull request, technical debt, refactoring, tooling or CI work) -> Engineering Task - Otherwise -> Others Engineering Task is not a GitHub issue form and is not offered to regular users. Only select it when the request clearly describes internal engineering work. **If unclear**, ask the user which template to use. Do not default to "Others" on your own. #### Eligibility Check (Engineering Task only) Engineering Task is meant for maintainers and collaborators with write access. This is a request, not an access control — nothing prevents anyone from calling `gh issue create` directly, and this skill does not try to. The check below is here so that a contributor without write access learns that early and gets pointed somewhere more useful. Before collecting any information, read the authenticated user's permission level: ```bash repo="$(gh repo view --json nameWithOwner...