github-issue-creator

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually creating GitHub issues often leads to inconsistent formatting, missing template fields, and shell escaping errors when passing multi-line Markdown through the command line. This Skill standardizes issue creation by following repository templates and using safe file-based body submission. ## Core Features & Use Cases - Template-Aware Drafting: Detects and reads issue templates from .github/ISSUE_TEMPLATE/, supporting both YAML forms and Markdown templates. - Safe CLI Submission: Writes issue bodies to temporary files and uses gh issue create --body-file to avoid shell escaping and formatting corruption. - Consistent Labeling: Applies the default maintainer only label to keep the backlog organized unless the user specifies otherwise. - Use Case: A developer discovers a bug in the CLI and asks the agent to file it; the Skill reads bug_report.yml, drafts all required fields including reproduction steps and version info, and creates a properly labeled issue with a shareable link. ## Quick Start Create a GitHub issue for the login timeout bug 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 to use GitHub issue templates when creating issues with gh CLI?

First locate templates in .github/ISSUE_TEMPLATE/, read the YAML form or Markdown file to learn required fields, then draft matching content. YAML forms can be filled with --field flags or submitted as a structured body.

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

Inline body strings passed through the shell often break on newlines, quotes, and special characters. Writing the body to a temporary file and using gh issue create --body-file preserves the exact Markdown formatting.

Does gh issue create support YAML issue forms?

Yes, gh issue create can target YAML forms, but non-interactive submission works best with --field flags for each form id, or by submitting a composed body when field-based submission is not required by repository automation.

What labels should be added when filing internal GitHub issues?

This workflow defaults to the maintainer only label so the backlog stays organized and triaged by the core team. You can override it by explicitly requesting different labels when the issue is created.