github-issue-creation

Classify user requests into Type and Language/Scope labels and create GitHub issues via CLI.

126|41|Updated Aug 4, 2018

Search Tags:#automation #github #classification #gh cli #issue #label-mapping

Ready to run

npx skills add https://github.com/hiromaily/go-crypto-wallet --skill github-issue-creation-hiromaily

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-creation
Source: https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/github-issue-creation
Command: npx skills add https://github.com/hiromaily/go-crypto-wallet --skill github-issue-creation-hiromaily

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to create GitHub issues with consistent task classification, ensuring the right Skills are engaged for each issue.

Core Features & Use Cases

Automatic classification of incoming requests into standard issue types (bug, enhancement, etc.) and language/scope labels.
Prerequisites integration with label-context-mapping to map labels to skills and context.
Proposal-driven creation: generate a structured issue proposal and push it to GitHub using the GitHub CLI.
Use Case: When a user reports a bug in XRP processing, the skill classifies it, proposes the issue details, and creates the GitHub issue with the appropriate labels.

Quick Start

From a user request, classify into Type and Language/Scope labels using label-context-mapping.
Generate a Proposed Issue with a title, labels, and body, then seek approval.
Run gh issue create to publish the issue with the assigned labels.

Frequently Asked Questions about github-issue-creation

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

FAQPage Schema

How do I automate GitHub issue creation with proper labels using the CLI?▼

Automating GitHub issue creation involves classifying user requests into Type and Language/Scope labels, generating a structured proposal, and executing GitHub CLI commands to publish the issue with the correct labels assigned.

What is the best way to classify GitHub issues automatically before creation?▼

Classifying GitHub issues automatically requires mapping user requests to standard issue types like bug or enhancement and language/scope labels, leveraging a label-context-mapping mechanism to determine appropriate follow-up actions.

Do I need the GitHub CLI to create issues with automatic classification?▼

Yes, GitHub CLI is required to publish the proposed issues. The workflow generates a structured issue proposal with a title, labels, and body, then uses the GitHub CLI to create the issue directly in the repository.

Can I generate an issue proposal for approval before pushing it to GitHub?▼

Yes, the workflow is proposal-driven. It generates a structured issue proposal containing the title, assigned labels, and body, allowing you to review and approve the details before executing the GitHub CLI creation command.

How does label-mapping determine the right follow-up actions for a new issue?▼

Label-mapping integrates with a label-context-mapping prerequisite to map assigned Type and Language/Scope labels to specific skills and context, ensuring the appropriate downstream actions are triggered for each created issue.

Why does my automated issue workflow lack consistent task classification?▼

Inconsistent task classification occurs when incoming requests are not mapped to standard issue types and language/scope labels, preventing the label-context-mapping mechanism from determining the correct follow-up actions and skills.