github-issue-creator

Creates GitHub issues using repository templates and the gh CLI with proper labeling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating well-structured GitHub issues that follow a repository's conventions is tedious: you must find the right template, fill in required fields, apply correct labels, and avoid shell-escaping errors with multi-line Markdown bodies. This Skill automates that entire workflow. ## Core Features & Use Cases - Template Detection: Locates and reads issue templates from .github/ISSUE_TEMPLATE/, supporting both YAML forms (bug_report.yml, feature_request.yml) and Markdown templates. - Safe Issue Creation: Writes issue bodies to temporary files and uses gh issue create --body-file to prevent newline and special-character corruption. - Consistent Labeling: Applies the 🔒 maintainer only label by default to keep the backlog organized. - Use Case: After discovering a bug in the CLI, ask the agent to file a bug report; it drafts the title and body from the repository's bug report template, creates the issue via gh, and returns the issue link. ## Quick Start Create a GitHub issue for the bug I just described using the repository's bug report template.

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 from the command line?

Use the gh CLI with gh issue create, passing a title and body. For multi-line Markdown bodies, write the content to a temporary file and pass it with --body-file to avoid shell escaping and formatting problems.

How do I use GitHub issue templates when creating an issue?

Look in the repository's .github/ISSUE_TEMPLATE/ directory for YAML forms like bug_report.yml or feature_request.yml, or Markdown templates. Read the template to learn the required fields, then draft your title and body to match its structure.

Why does my GitHub issue body lose formatting when created via CLI?

Multi-line text and special characters get mangled by shell escaping when passed inline. Write the body to a temporary file first and use gh issue create --body-file, then delete the temporary file afterward.

Does gh issue create support YAML issue forms?

YAML forms are designed for the web interface, but gh can submit content via --body, --body-file, or --field flags. For repositories using YAML forms, submitting a structured single body often works when field-based submission is not enforced.

What labels should I add when filing a GitHub issue?

Follow the repository's conventions. In this workflow the default label is "🔒 maintainer only", applied to every issue unless the user explicitly requests a different label.