git-issuelisted

# Git issue Format an issue from session context following the issue standard, then file it on the current repository with `gh issue create`. ## Context Read these in parallel: - `${CLAUDE_SKILL_DIR}/../../standards/issue.md`: issue title, labels, body sections, and banned phrases - `${CLAUDE_SKILL_DIR}/../../standards/markdown.md`: banned words, punctuation, and formatting for all generated text - The `write-human` skill: voice, rhythm, and sentence construction for all generated text Then gather repo context in parallel: - `git remote get-url origin 2>/dev/null || echo "NO_REMOTE"` - `gh auth status >/dev/null 2>&1 && echo "AUTHED" || echo "NO_AUTH"` ## Guards - If nothing in session context describes a concrete bug or task, stop: `❌ No issue in session context. Describe the bug or task, then re-invoke.` - If `git remote get-url origin` returns `NO_REMOTE`, stop: `❌ No GitHub remote. gh issue create needs an origin.` - If `gh auth status` returns `NO_AUTH`, stop: `❌ gh is not authenticated. Run gh auth login.` - If the type is ambiguous between a bug and a task, ask one line before formatting. ## Response format ### Preview - **Title:** `<type>: <subject>` - **Label:** <bug or enhancement> - **Analysis:** <one line on what the issue captures> After outputting the preview, execute the final command immediately. Claude Code's tool permission dialog is the confirmation gate. Do not wait for user input. ### Pre-publish scan Before running the final command, run th