github-issue-creator

Create GitHub issues using repository templates and maintainer-specific labels.

6|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Ven0m0/claude-config --skill github-issue-creator-ven0m0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/Ven0m0/claude-config/tree/main/.gemini/skills/github-issue-creator
Command: npx skills add https://github.com/Ven0m0/claude-config --skill github-issue-creator-ven0m0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the creation of GitHub issues by ensuring they adhere to repository standards, utilize appropriate templates, and are correctly labeled, reducing manual effort and improving issue quality.

Core Features & Use Cases

  • Template Utilization: Automatically finds and uses predefined issue templates (.github/ISSUE_TEMPLATE/).
  • Type Identification: Differentiates between bug reports, feature requests, and other issue types.
  • Labeling: Applies default labels (e.g., 🔒 maintainer only) and handles custom labeling.
  • Robust Content Handling: Uses temporary files to prevent formatting issues with multi-line or complex issue bodies.
  • Use Case: When a user reports a bug, this skill will prompt for details, find the bug_report.yml template, populate it, and create the issue on GitHub with the correct title, body, and labels.

Quick Start

Use the github-issue-creator skill to create a new bug report issue.

Frequently Asked Questions about github-issue-creator

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

FAQPage Schema
How do I create a GitHub issue using repository templates automatically?

To create a GitHub issue using repository templates, this skill locates predefined templates in the `.github/ISSUE_TEMPLATE/` directory, populates them with your input, and submits the issue via the `gh` CLI with correct labeling.

What is the best way to handle multi-line content when creating a GitHub bug report?

Handling multi-line content for a GitHub bug report requires writing the issue body to temporary files before submission, which prevents formatting issues and preserves complex text structures when using the `gh` CLI.

Can I apply custom labels like maintainer-only tags when creating GitHub issues?

Yes, you can apply custom labels when creating GitHub issues; the skill automatically applies default labels such as `🔒 maintainer only` and supports custom labeling to ensure organized backlog management.

Does the GitHub issue creation process support differentiating between bug reports and feature requests?

Yes, the GitHub issue creation process differentiates between bug reports and feature requests by identifying the issue type and selecting the corresponding template, such as `bug_report.yml`, to populate and submit.

Why do I need the gh CLI to automate GitHub issue creation from templates?

You need the `gh` CLI to automate GitHub issue creation because it handles repository authentication, template population, and the direct submission of titles, bodies, and labels to the GitHub repository.

What are the limitations of using template files for GitHub issue creation?

Using template files for GitHub issue creation requires that templates already exist in the `.github/ISSUE_TEMPLATE/` directory, and the skill relies on the `gh` CLI environment being properly authenticated to function correctly.