create-issue

Create GitHub issues with conventional commit titles, labels, and sub-issues.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Emmanuelkwaa/NetRockTemplate --skill create-issue-emmanuelkwaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/Emmanuelkwaa/NetRockTemplate/tree/main/.claude/skills/create-issue
Command: npx skills add https://github.com/Emmanuelkwaa/NetRockTemplate --skill create-issue-emmanuelkwaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of GitHub issues, streamlining bug tracking and feature management by intelligently inferring details and formatting.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub issues with conventional commit titles, detailed bodies, and relevant labels.
  • Intelligent Inference: Automatically determines issue type, scope, and labels from the provided context.
  • Sub-issue Management: Can split complex tasks into multiple sub-issues and link them to a parent issue.
  • Use Case: When a bug is reported, use this Skill to create a well-formatted GitHub issue with fix type, relevant labels like bug and backend, and a clear description of the problem and proposed solution.

Quick Start

Use the create-issue skill to make a new GitHub issue for a reported bug in the user authentication system.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I automate GitHub issue creation from a bug report?

To automate GitHub issue creation, you can use an issue generation tool that infers the type, scope, and labels directly from your bug report context, automatically formatting the title and body for you.

What is the best way to format GitHub issue titles for feature requests?

The best way to format GitHub issue titles is using Conventional Commit format, which clearly defines the type, such as feature or fix, and scope to maintain a consistent and readable issue tracking history.

Can I automatically split a complex task into sub-issues on GitHub?

Yes, you can split complex tasks into sub-issues and link them to a parent issue. This is achieved by using the GitHub CLI to manage the hierarchy and relationships between the main task and its sub-components.

How are GitHub issue labels like backend or frontend automatically determined?

GitHub issue labels like backend, frontend, security, and documentation are automatically determined by inferring the context of the task, analyzing the description to apply the most relevant tags without manual input.

Do I need the GitHub CLI to manage sub-issues and parent issue linking?

Yes, you need the GitHub CLI to manage sub-issues and parent issue linking, as it provides the necessary command-line interface to programmatically create and link complex issue hierarchies.