github-issues

Plan and organize GitHub issues with types, dependencies, and sub-issues.

Updated Aug 8, 2021
One-click install
npx skills add https://github.com/luanzeba/dotfiles --skill github-issues-luanzeba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/luanzeba/dotfiles/tree/main/skills/github-issues
Command: npx skills add https://github.com/luanzeba/dotfiles --skill github-issues-luanzeba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams plan, organize, and track work in GitHub by using issue types, dependencies, and sub-issues, ensuring proper workflow boundaries and visibility.

Core Features & Use Cases

  • Define issue types (Epic, Batch, Task, Bug) and apply structured workflows to groups of work.
  • Create parent-child relationships with Sub-Issues and Batch tasks, and link issues via dependencies for clear blocking relationships.
  • Guidance on formatting and writing issues to avoid repetition, plus inline references to API workflows for dependencies and sub-issues.

Quick Start

Create a parent Epic issue, then add child Tasks and link them as dependencies or sub-issues using the GitHub Issues API.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I manage GitHub issues with dependencies and sub-issues?

To manage GitHub issues with dependencies, you can create parent-child relationships using sub-issues and link blocking relationships via the GitHub Issues API. This ensures clear workflow boundaries and visibility for complex feature work.

What is the best way to organize GitHub Epics, Batches, and Tasks for sprint planning?

The best way to organize GitHub issues for sprint planning is to define issue types like Epic, Batch, and Task. You can then apply structured workflows and establish hierarchies to properly size sprints and track complex feature work.

Can I create parent-child relationships for GitHub issues using the GraphQL API?

Yes, you can build, update, and query parent-child relationships for GitHub issues using the GraphQL API. This allows you to structure complex feature work by linking sub-issues under parent Epics.

How do I write effective GitHub issue descriptions to avoid repetition?

To write effective GitHub issue descriptions and avoid repetition, follow structured formatting guidance that clearly defines the issue type and its dependencies. This maintains proper workflow boundaries and project visibility.

When should I use GitHub sub-issues instead of dependencies for project management?

Use GitHub sub-issues to establish parent-child hierarchies for grouped work like Epics and Tasks, whereas dependencies are used to link separate issues that block each other. Applying both ensures clear tracking and structured workflows.