skills.rest
o3-ozono
o3-ozonoCOMMUNITY
Explore all skills by this author →
GitHub

issue

Auto-detect task type and create labeled issues from user requests.

Updated Aug 27, 2026
Search Tags:#automation#templates#ideation#github#issue#workflows
One-click install
npx skills add https://github.com/o3-ozono/atdd-kit --skill issue-o3-ozono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/o3-ozono/atdd-kit/tree/main/skills/issue
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill issue-o3-ozono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-triggers when users request new features, improvements, or tasks by turning natural language prompts into tracked issues, ensuring requirements are captured and routed correctly.

Core Features & Use Cases

  • Auto-detects task type (development, bug, research, documentation) and selects an appropriate issue template.
  • Creates the Issue, adds the correct type label, and posts a contextual summary for traceability.
  • Chains the new Issue to an ideation flow for design exploration before requirements are finalized.
  • Supports structured priority handling and guidance for downstream work.

Quick Start

Create an Issue from a user request by auto-detecting the type, selecting the template, and starting ideation.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I automate GitHub issue creation from natural language prompts?▼

Automating GitHub issue creation involves auto-detecting the task type from natural language prompts, selecting an appropriate issue template, and applying the correct type label for proper routing. This captures user requests for features, bugs, or research and turns them into tracked issues.

Can I automatically label and route issues based on the task type?▼

Yes, automatically label and route issues by detecting whether the request is a bug report, feature request, documentation update, or research task. The system applies a type-appropriate label and uses guardrails to ensure proper prioritization and routing.

What is the best way to chain issue creation to an ideation workflow?▼

Chain issue creation to an ideation workflow by linking the newly created issue to a design exploration flow before finalizing requirements. This allows for structured ideation directly after the initial issue intake and ensures proper template application.

Does this issue automation approach work for both bug reports and documentation updates?▼

Yes, this issue automation approach works for bug reports, documentation updates, feature requests, and research tasks. It auto-detects the specific request type and selects the corresponding template to capture requirements accurately.

Do I need predefined templates to automate issue intake and prioritization?▼

Yes, predefined templates are required to automate issue intake and prioritization effectively. The automation relies on these templates alongside type-appropriate labels and guardrails to ensure proper prioritization and routing of the captured requests.

Related Skills

Explore More Software Engineering Skills→
KanevryKanevry
50

gitlab-ops

Standardize GitLab and GitHub CLI usage with dynamic project resolution.

Community
Intermediate
ctoscanoctoscano

prd

Create and track Product Requirement Documents through structured status workflows.

Community
Advanced
pacphipacphi
6

test-automation-strategy

Design test automation frameworks with pyramid distribution and CI/CD integration.

Community
Advanced
MithrilManMithrilMan

gh-resolve-issue

Triage and resolve GitHub issues using the gh CLI.

Community
Advanced