issue-create

Generate GitHub issues with mapped labels and YAML frontmatter.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill issue-create-apokamo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-create
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-create
Command: npx skills add https://github.com/apokamo/kaji --skill issue-create-apokamo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Issue Create skill automates the generation of GitHub issues and assigns appropriate labels to kickstart development workflows, ensuring a consistent starting point for new work items.

Core Features & Use Cases

  • Generates GitHub issues from a structured input including title, type, and optional description.
  • Maps types to standard labels (feat/fix/refactor/docs/etc.) to align with project conventions.
  • Supports integration with the review-ready guidelines to ensure the issue body meets quality criteria.

Quick Start

Run kaji issue create with a descriptive title and optional type to generate a labeled GitHub issue.

Frequently Asked Questions about issue-create

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

FAQPage Schema
How do I automate GitHub issue creation with proper labels for new features?

To automate GitHub issue creation, the skill generates a structured issue body with standardized YAML frontmatter and maps input types to standard labels like feat or fix. This ensures every new feature or bug fix has a consistent starting point.

How does auto-assigning labels work when generating issues for bug fixes or refactors?

Auto-assigning labels works by mapping your specified issue type, such as fix or refactor, to the corresponding standard project labels. The generated issue body is then output with these labels applied to align with your repository conventions.

Can I use templates to generate a GitHub issue body that meets review-ready guidelines?

Yes, you can generate a GitHub issue body using templates that enforce standard YAML frontmatter. This structured output aligns with review-ready guidelines, ensuring the issue body meets quality criteria before submission.

What is the best way to standardize issue formatting across new development workflows?

The best way to standardize issue formatting is to enforce a standard YAML frontmatter with name and description fields. Using templates for content ensures every generated issue body maintains a consistent structure for development workflows.

Do I need a specific type input to map to standard labels like docs or feat?

Yes, you need to provide an optional type input such as docs or feat to map it to standard labels. This mapping automatically assigns the correct labels to the generated issue, aligning it with project conventions.