Create and manage GitHub issues with guided workflows

This skill helps a user create, list, or view GitHub issues by driving an interactive question-and-answer flow and then running the matching gh issue command. For creating an issue, it asks for the issue type (bug, enhancement, new feature, task), gathers a short title (5-10 words) plus a detailed description, and for bug reports also collects reproduction steps and expected-vs-actual behavior. It composes the issue body from a type-specific template (bug, feature/enhancement, or task) plus optional labels (bug, enhancement, documentation, good first issue), then runs gh issue create with a HEREDOC body so formatting and newlines are preserved. For listing, it asks how to filter (all open issues, assigned to me, created by me, or by label) and runs the matching gh issue list variant. For viewing, it asks for an issue number and runs gh issue view.

Use it whenever a task involves creating, inspecting, or triaging GitHub issues in a repository already set up with the gh CLI - it is meant to guide the intake conversation (title, type, description, repro steps, labels) rather than have the user type a full issue body unassisted. It is not a substitute for environment-specific validation, testing, or expert review, and the skill's own limitations say to stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Inputs are gathered entirely through a sequence of guided prompts: which action to take (create, list, or view), the issue title, issue type, full description, reproduction steps and expected/actual behavior for bugs, labels to apply, a list filter (all, assigned, created, or by label), or an issue number to inspect. Outputs are gh CLI invocations - gh issue create --title ... --body ... --label ..., gh issue list (optionally with --assignee @me, --author @me, or --label), and gh issue view [number] - plus the resulting issue URL or issue details (title, body, labels, assignees, comments) reported back to the user.

Built entirely on the GitHub CLI (gh), specifically gh issue create, gh issue list, and gh issue view. It also checks gh auth status and instructs the user to run gh auth login if authentication is missing, and it assumes the working directory is a git repository with a GitHub remote.

Developers and teams working inside a GitHub-backed repository who want a guided, conversational way to file well-structured bug reports and feature requests, browse or filter existing issues, or pull up a specific issue's details, without having to remember gh command syntax or draft an issue body from scratch.