create-issue

You can automate GitHub issue generation by applying standardized templates with predefined frontmatter for tasks, bugs, and features. This skill validates metadata and handles labels before posting, ensuring consistent issue quality across multiple repositories.

To prevent unintended changes during GitHub issue posting, this skill enforces an interactive confirmation step. It requires explicit user consent before submitting any generated issue to a repository, safeguarding against accidental automation.

Yes, GitHub CLI integration supports label handling for automated issue creation. The process validates metadata and applies standardized labels derived from templates, ensuring consistent categorization across tasks, bugs, epics, and features.

The best way to standardize task, bug, and epic issues across multiple repositories is template-driven generation. By relying on predefined frontmatter and strict label validation, teams can ensure consistent issue quality and metadata management.

To start generating templated GitHub issues, you run the designated slash command. This initiates the template discovery process, applies validation and label handling, and prompts for explicit confirmation before posting the issue.

You should not use automated workflows for GitHub issue generation when drafting requires inconsistent, ad-hoc prompts or manual freeform input. This approach strictly relies on standardized templates and explicit confirmation, limiting freeform issue creation.