github-issue-creator

Draft GitHub issues from repository templates using the gh CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JansonXIE/sophon_cli --skill github-issue-creator-jansonxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/JansonXIE/sophon_cli/tree/main/.gemini/skills/github-issue-creator
Command: npx skills add https://github.com/JansonXIE/sophon_cli --skill github-issue-creator-jansonxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly create well-formed GitHub issues by leveraging repository templates and consistent labeling to reduce ambiguity and manual drafting time.

Core Features & Use Cases

  • Searches for issue templates in .github/ISSUE_TEMPLATE/ (e.g., bug_report.yml, feature_request.yml) and reads their fields to populate a new issue.
  • Drafts the issue title and body according to the selected template and applies a default maintainer label to streamline prioritization.
  • Use Case: A developer receives a request to report a bug and uses this skill to generate a ready-to-submit issue with the correct fields and formatting.

Quick Start

Draft a GitHub issue using the repository's templates and labeling rules.

Frequently Asked Questions about github-issue-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically create GitHub issues from repository templates?

This skill reads YAML templates from .github/ISSUE_TEMPLATE/, populates fields, applies default labels, and uses the gh CLI to create issues. It enforces standards and reduces manual drafting time.

What is the best way to enforce consistent formatting and labels for GitHub issues?

The best way to enforce consistent GitHub issue formatting is to generate issues directly from repository templates. This skill drafts titles and bodies from template fields and automatically applies maintainer labels to streamline prioritization.

How does the gh CLI interact with GitHub issue templates?

The gh CLI interacts with GitHub issue templates by executing the final issue creation command. The skill reads the template structure, drafts the body, and invokes the gh CLI to submit the formatted issue to the repository in a controlled manner.

Do I need existing ISSUE_TEMPLATE files to automatically draft a bug report?

Yes, you need existing ISSUE_TEMPLATE files in the .github/ISSUE_TEMPLATE/ directory, such as bug_report.yml. The skill searches for these files and reads their fields to populate the new bug report with correct formatting.

Can I use this approach to create feature requests across multiple repositories?

Yes, this skill is applicable when requesting bug reports, features, or tasks across repositories. As long as the repository contains ISSUE_TEMPLATE files, it will read the fields and generate a ready-to-submit feature request.

What are the limitations of using templates for GitHub issue tracking automation?

A limitation of using templates for GitHub issue tracking automation is that the skill depends on pre-existing ISSUE_TEMPLATE files to function. Without properly configured templates and the gh CLI, it cannot draft or create the standardized issues.