issue

Generate structured GitHub Issues with title, description, and acceptance criteria.

Updated Apr 30, 2025
One-click install
npx skills add https://github.com/a-tabiji/atima-lp --skill issue-a-tabiji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/a-tabiji/atima-lp/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/a-tabiji/atima-lp --skill issue-a-tabiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of consistent GitHub Issues by organizing task purpose, acceptance criteria, and related sections into a clear, ready-to-submit ticket.

Core Features & Use Cases

  • Template-driven Issue generation with sections for Summary, Description, Acceptance Criteria, and References.
  • Automatic classification of the issue type (bug, enhancement, etc.) based on input context.
  • Direct prompts to create issues from briefs, product specs, or user stories across software projects.

Quick Start

Provide the issue title and an optional description, and I will generate a structured GitHub Issue ready for publishing.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I generate a structured GitHub Issue from a brief?

To generate a structured GitHub Issue from a brief, provide the issue title and an optional description. The tool automatically composes the title, description, acceptance criteria, and references into a ready-to-submit ticket.

What is the best way to automate GitHub ticket creation for bugs and improvements?

Automating GitHub ticket creation for bugs and improvements involves using a template-driven generation process. It automatically classifies the issue type based on input context and organizes task purpose and acceptance criteria into a clear ticket.

Does this issue generation workflow support standard frontmatter metadata blocks?

Yes, this issue generation workflow enforces a standard frontmatter-defined metadata block. It produces a ready-to-submit body compatible with GitHub's issue creation workflow, ensuring consistent formatting across all generated tickets.

Can I use briefs or user stories to draft GitHub Issues for software projects?

Yes, you can use briefs, product specs, or user stories to draft GitHub Issues across software projects. The tool provides direct prompts to create issues from these concise inputs, organizing them into structured sections.

What sections are included in a template-driven GitHub Issue?

A template-driven GitHub Issue includes sections for Summary, Description, Acceptance Criteria, and References. This structure streamlines the creation of consistent tickets by organizing task purpose and related details clearly.