skills.rest
divinevideo
divinevideoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

github-issue

Create GitHub issues following Epic, Feature, Task, and Bug hierarchy templates.

262|51|Updated Jun 15, 2025
Search Tags:#templates#github#issues#feature#epic#task
One-click install
npx skills add https://github.com/divinevideo/divine-mobile --skill github-issue-divinevideo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue
Source: https://github.com/divinevideo/divine-mobile/tree/main/.claude/skills/github-issue
Command: npx skills add https://github.com/divinevideo/divine-mobile --skill github-issue-divinevideo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue creation is often inconsistent; this skill enforces an Epic > Feature > Task/Bug hierarchy and uses issue types and relationship links to connect related work for clearer planning and traceability.

Core Features & Use Cases

  • Enforces a standardized issue hierarchy (Epic -> Feature -> Task/Bug) to improve planning and traceability.
  • Uses GitHub issue types (Epic, Feature, Task, Bug) and relationship links (Parent/Child, Related to, Blocks, Blocked by) to connect related work.
  • Provides templates and guidance to draft issues that align with team conventions and auto-forms.

Quick Start

Describe the issue to create a properly structured Epic/Feature/Task/Bug in GitHub using the recommended templates.

Frequently Asked Questions about github-issue

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

FAQPage Schema
How do I create well-structured GitHub issues that follow a specific hierarchy?▼

Creating well-structured GitHub issues involves applying an Epic > Feature > Task/Bug hierarchy with defined issue types. You can connect related work using relationship links like Parent/Child, Related to, Blocks, and Blocked by to improve planning and traceability.

How do I link related GitHub issues to improve planning and traceability?▼

You can link related GitHub issues by defining relationship links such as Parent/Child, Related to, Blocks, and Blocked by. Connecting related work within an Epic > Feature > Task/Bug hierarchy enforces team conventions and improves overall project traceability.

What is the best way to enforce consistent GitHub issue templates across a project?▼

The best way to enforce consistent GitHub issue templates is to use a standardized hierarchy of Epic, Feature, Task, and Bug types. This ensures issues align with team conventions and auto-forms, providing guidance and consistent structure across all project issues.

Does this GitHub issue hierarchy support linking Bugs to parent Features?▼

Yes, the GitHub issue hierarchy supports linking Bugs to parent Features using Parent/Child relationship links. This organizes work into an Epic > Feature > Task/Bug structure, ensuring clear traceability and proper connection of related tasks across projects.

When do I need to use Epic, Feature, and Task issue types in GitHub?▼

You need to use Epic, Feature, and Task issue types in GitHub when organizing work for product teams and developers. Applying this hierarchy ensures issues follow team templates, links related work, and provides clear planning and traceability across development projects.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
NourcineAbNourcineAb

github-project-management

Automate GitHub issue tracking, board synchronization, and sprint planning workflows.

Community
Advanced
shaman007shaman007
25

speckit-taskstoissues

Parse task identifiers from spec-kit documentation and create GitHub issues.

Community
Advanced
gosu-codegosu-code
1

task-list-md

Parse and manage hierarchical Markdown task lists with a Python CLI.

Official
Advanced