kata-contributing-issue

Create templated GitHub issues with required labels and issue type metadata.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-contributing-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-contributing-issue
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-contributing-issue
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-contributing-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create a correctly structured GitHub issue in the origin repository by selecting the right template, filling required fields, and applying repository-required labels and issue type metadata.

Core Features & Use Cases

  • Issue-Type Selection & Template Loading: Determines the appropriate issue type (feature request, epic, user story API/frontend, simple task) and loads the corresponding contributing template from the Ahrena templates path with fallbacks.
  • Guided Template Filling: Collects the information needed to replace placeholders in the template and generates a complete Markdown issue body and title.
  • Creation + Required Governance: Creates the issue via GitHub MCP (preferred) or gh CLI (fallback), sets the repository-specific GitHub Issue Type via GraphQL, and applies the mandatory status: todo label without assigning an assignee.

Quick Start

Ask the AI to open a "feature request" issue for design-system by creating a templated GitHub issue with the required labels and setting the GitHub issue type immediately after creation.

Frequently Asked Questions about kata-contributing-issue

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

FAQPage Schema
How do I create a GitHub issue with a specific template and required labels?

You can create a templated GitHub issue by providing the issue type and context, which loads the correct template, fills placeholders, sets the issueTypeId via GraphQL, and applies required labels like status: todo.

What is the best way to automate GitHub issue creation for feature requests and epics?

Automating GitHub issue creation involves selecting an issue type like feature request or epic, loading the contributing template, and generating a structured Markdown body with mandatory governance labels applied automatically.

Does this issue creation workflow support setting the GitHub issue type via GraphQL?

Yes, this workflow sets the repository-specific GitHub Issue Type via GraphQL immediately after issue creation, ensuring the issueTypeId is correctly assigned alongside the mandatory status: todo label.

Can I use gh CLI as a fallback when GitHub MCP fails to open a templated issue?

Yes, the gh CLI serves as a fallback for creating the GitHub issue when the preferred GitHub MCP method fails, ensuring the templated issue body and mandatory labels are still applied correctly.

What issue types are supported when loading contributing templates?

Supported issue types include feature request, epic, user story API/frontend, and simple task, each mapping to a specific contributing template loaded from the templates path to ensure consistent structure and governance.

Why does my automated GitHub issue creation avoid setting an assignee?

Automated GitHub issue creation avoids setting an assignee to maintain workflow governance, ensuring the issue is created with the correct type and status: todo label for triage rather than being immediately assigned to a specific developer.