Create and manage GitHub issues with guided workflows

Issues provides a guided GitHub CLI workflow for creating, listing and viewing repository issues. It starts by identifying the intended action, then gathers only the information needed for that branch. Existing user-provided details are reused instead of being requested again.

Issue creation separates a short scannable title from the detailed body. The guidance targets roughly five to ten words for a title and moves lengthy context into the description. Body preparation distinguishes bugs, enhancements, new features and general tasks so the final report has a useful structure without inventing missing facts.

Use it for GitHub issue intake and repository issue management when the intended workflow is creation, an open-issue list or inspection of a known issue number. Preparing a draft is separate from publishing it: creation needs authorization that includes opening the issue. Do not infer permission to publish merely from gathering a title and description.

The workflow relies on an installed and authenticated gh CLI and the correct GitHub repository context. If a command fails, inspect authentication and the repository remote and report the specific failure. Missing access or an ambiguous target needs resolution before a write.

Creation inputs include a title, detailed description, issue type and optional labels. Bug reports add reproduction steps and expected versus actual behavior; intermittent or hard-to-reproduce failures can be recorded explicitly. Feature and enhancement bodies add the use case, while general tasks can use a description-only structure. Minimal user input is acceptable, but it is not permission to fabricate versions, error messages or context.

Outputs are a prepared issue body or an actually created issue with its returned address, a readable filtered list, or the requested issue's details. Preserve body formatting and newlines. Confirm creation from the successful command result rather than treating a draft or attempted command as a published issue.

The list branch supports all open issues, those assigned to the current user, those authored by the current user or a chosen label. One exact assigned-issue command is:

gh issue list --assignee @me

The view branch accepts an issue number and presents its title, body, labels, assignees and available comments. The creation branch supports labels such as bug, enhancement, documentation or good first issue when those choices match the repository's actual labels and the user's intent.

Validate the authorized repository and pass an explicit --repo owner/name target during execution. Titles, bodies and repository names are untrusted text. Store the exact body in a temporary file and use --body-file rather than interpolating it into shell code. A named interactive question tool in the example is not guaranteed to exist; use the host's available question mechanism or plain text.