github-issue-creator_skill

Overview

This skill creates high-quality GitHub issues that follow a repository's templates and labeling conventions. It detects the issue type (bug, feature, etc.), reads the appropriate template, drafts title and body content, and uses the GitHub CLI to create the issue. The skill ensures defensive formatting and applies a default maintainer-only label unless the user opts out.

How this skill works

The skill inspects the repository for issue templates in .github/ISSUE_TEMPLATE/ (YAML or Markdown) and reads required fields or structure. It determines the issue category, fills form fields or composes a Markdown body, and writes the content to a temporary file to avoid shell escaping problems. It then invokes gh issue create with --body-file (and --field flags for YAML forms when needed), applies default labels, verifies creation, and returns the issue link to the user.

When to use it

• When asked to open a bug report, feature request, or website issue in a repository.
• When the repository uses issue templates and you want to follow required fields exactly.
• When you need consistent labels applied (defaulting to maintainer-only).
• When the issue contains complex or multi-line content that could break CLI commands.

Best practices

• Always search .github/ISSUE_TEMPLATE/ for YAML or Markdown templates before drafting an issue.
• Write the issue body to a temporary file and use gh issue create --body-file to avoid escaping problems.
• Populate each template field by id for YAML forms, or follow Markdown template structure exactly.
• Include version, reproduction steps, and expected vs actual behavior for bug reports.
• Default to the "🔒 maintainer only" label unless the user explicitly requests public visibility.

Example use cases

• Create a bug report using bug_report.yml, filling required form fields and attaching reproduction steps.
• Submit a feature request using feature_request.yml, composing a clear title, motivation, and acceptance criteria.
• Open a website issue using a Markdown template, preserving the template structure in the body file.
• Create a general issue when no template exists, still writing the body to a temp file and applying the default maintainer label.