github-issue-creation

Create GitHub issues via gh CLI with a body file and at least one label.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jarodmeng/daydreamedu-scripts --skill github-issue-creation-jarodmeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-creation
Source: https://github.com/jarodmeng/daydreamedu-scripts/tree/main/.cursor/skills/github-issue-creation
Command: npx skills add https://github.com/jarodmeng/daydreamedu-scripts --skill github-issue-creation-jarodmeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool creates GitHub issues using the gh CLI, ensuring the body is provided via a body file and that each issue includes at least one label.

Core Features & Use Cases

  • Create issues in any repository from the current directory or a specified owner/repo.
  • Enforce body-file usage and label requirements to improve consistency and traceability.
  • Works in automation workflows and manual commands to quickly file issues or draft proposals.

Quick Start

When you need to file an issue, provide a title and a body via a file, and attach at least one label before creating the issue.

Frequently Asked Questions about github-issue-creation

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

FAQPage Schema
How do I create GitHub issues from a body file using the gh CLI?

To create GitHub issues from a body file, this tool automates the gh CLI to read content from a specified file, ensuring separation of issue text from commands. It works in any specified owner/repo or the current git context.

Do I need to add labels when creating issues with the gh CLI?

Yes, you need to add labels when creating issues. The tool enforces at least one label for each issue to improve consistency and traceability before submitting the request via the gh CLI.

Can I automate bug report creation in any repository from my current directory?

You can automate bug report creation in any repository by providing an owner/repo argument. If no repository is specified, the tool defaults to the current git context to file the issue.

What's the best way to ensure consistent issue formatting in GitHub automation workflows?

The best way to ensure consistent issue formatting is to enforce body-file usage. This tool mandates providing issue content through a file rather than inline strings, maintaining consistent structure across feature requests and bug reports.

Why does my GitHub issue creation fail without a body file?

GitHub issue creation fails because the tool enforces body-file usage to maintain consistency. It requires the issue body to be stored in a separate file and will not process inline text submissions.