create-github-issue

Drafting GitHub issues from repository templates involves reading .github/ISSUE_TEMPLATE/*.yml files, matching your intent to a form, and generating a formatted body. The skill parses YAML fields to gather reproduction steps and environment details for a ready-to-paste draft.

Matching a bug report to a YAML issue template requires reading the template's name and description to align with user intent. The system then parses the selected YAML form fields to collect the necessary reproduction steps and environment details for the final issue draft.

Yes, this issue drafting approach works with feature requests and RFCs. It applies to bug, feature, documentation, RFC, or maintenance issue types by reading the available .github/ISSUE_TEMPLATE/*.yml files and matching the provided intent to the appropriate repository template.

You can use this to generate issue drafts for any GitHub repository that contains .yml files within the .github/ISSUE_TEMPLATE/ directory. The skill reads these existing YAML forms to ensure the generated output respects the specific formatting and guidelines of that repository.

The best way to ensure consistent formatting across GitHub issues is leveraging the repository's existing YAML templates. By parsing the .github/ISSUE_TEMPLATE/*.yml forms and gathering required context, the generated draft respects safety considerations and project conventions automatically.

When drafting issues, the skill explicitly ignores config.yml files and only reads .github/ISSUE_TEMPLATE/*.yml. A limitation is that drafts are constrained to the fields defined in those YAML forms, requiring the repository to have valid templates for the intended issue type.