create-issue

Create GitHub issues with automatic type, area, and priority labels.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill create-issue-webdevcody
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/create-issue
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill create-issue-webdevcody

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the time-consuming work of manually creating GitHub issues by taking a short description, automatically classifying it with consistent labels, and then creating the issue for you.

Core Features & Use Cases

  • Auto-classification across axes: Applies dominant labels for type, area, and optional priority based on the description you provide.
  • Repo label hygiene: Checks whether the required labels already exist and creates missing labels with a consistent color scheme only after your confirmation.
  • Safer issue creation workflow: Uses a mandatory confirmation gate so you can edit or cancel before any issue or label changes happen.

Example: You notice an endpoint error happens after a recent change; describe it in one sentence and the skill drafts a bug issue with backend/infra-appropriate labels and a clear acceptance-criteria body.

Quick Start

Ask the AI to “create an issue” and provide a brief, one-sentence description of what’s wrong or what you want to add.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create a GitHub issue from a natural language description?

Creating a GitHub issue from a natural language description involves automatically classifying your text into type, area, and priority labels, then generating the issue via the GitHub CLI with a formatted acceptance-criteria body.

What is the best way to automate GitHub issue labeling?

Automating GitHub issue labeling is best handled by auto-classifying a short description into dominant type, area, and priority labels, ensuring consistent color schemes by creating missing labels only after a confirmation gate.

Do I need the GitHub CLI to automate issue creation?

Yes, the GitHub CLI is required to automate issue creation, as the skill validates GitHub access and executes the final issue creation command with the finalized title, labels, and body through the CLI.

Can I review labels before a GitHub issue is automatically created?

You can review labels before a GitHub issue is created because the skill enforces a mandatory confirmation gate, allowing you to edit or cancel the issue and label changes before they happen.

What types of GitHub issues can be auto-generated from text?

Auto-generated GitHub issues from text can apply to bug reports, feature requests, enhancements, refactors, documentation needs, and operational improvements where label-based triage is desired.