issue

Create formatted GitHub Issues with templates and labels via gh CLI.

4|Updated Dec 31, 2025

Search Tags:#automation #templates #github #cli #quality #issue

Ready to run

npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill issue-taketo-yoda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/Taketo-Yoda/uv-sbom/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill issue-taketo-yoda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create GitHub Issues with consistent formatting and sufficient technical detail for autonomous implementation.

Core Features & Use Cases

Template-based issue creation for Feature, Bug, and Documentation tasks, enforcing English language across title, body, labels, and comments.
Guided data collection: Type, Summary, Context, and Technical Details to ensure complete issue descriptions.
Validation and automation: verifies completeness before submission and uses the gh CLI to create issues with proper labels.

Quick Start

Provide the issue details and let this skill generate a well-formatted English GitHub Issue and create it via gh.

Frequently Asked Questions about issue

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

FAQPage Schema

How do I create well-structured GitHub Issues with consistent formatting?▼

To create well-structured GitHub Issues, use a template-based generator that gathers Type, Summary, Context, and Technical Details, then validates completeness before submission via the gh CLI.

Does the issue generation process work with the gh CLI for automation?▼

Yes, the issue generation process works with the gh CLI by using it to automatically create issues with proper labels and enforced English formatting for autonomous implementation.

What is the best way to format bug reports and feature requests for autonomous implementation?▼

The best way to format bug reports and feature requests is using structured templates that collect Type, Summary, Context, and Technical Details to ensure complete issue descriptions for autonomous implementation.

Can I use this skill to enforce English language across GitHub Issue titles and labels?▼

Yes, you can use this skill to enforce English language across issue titles, bodies, labels, and comments, ensuring consistent formatting across feature, bug, and documentation tasks.

Do I need to provide technical details when creating a GitHub Issue through this guided process?▼

Yes, you need to provide technical details because the guided data collection requires Type, Summary, Context, and Technical Details to validate completeness before submitting the issue.