zoonk-github-issues

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

146|12|Updated Jan 30, 2025
One-click install
npx skills add https://github.com/zoonk/zoonk --skill zoonk-github-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoonk-github-issues
Source: https://github.com/zoonk/zoonk/tree/main/.agents/skills/zoonk-github-issues
Command: npx skills add https://github.com/zoonk/zoonk --skill zoonk-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue management can be tedious when coordinating types, dependencies, and sub-issues across multiple tasks; this skill centralizes planning and governance of issues in a scalable way.

Core Features & Use Cases

  • Create and manage GitHub issues with support for issue types, dependencies, and sub-issues. For planning, reference the zoonk-issue-planning guidance to structure work.
  • Link related issues as sub-issues and establish dependencies to enforce order and progress tracking.

Quick Start

Create an initial issue with a clear title and description, then link related tasks as sub-issues and define dependencies as needed.

Frequently Asked Questions about zoonk-github-issues

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

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

You can manage GitHub issues by creating a primary issue and then linking related tasks as sub-issues. This skill uses GraphQL mutations to establish dependencies and enforce task order for coordinated release planning.

Can I assign issue types to GitHub issues using the gh CLI?

Yes, you can assign issue types to GitHub issues using the gh CLI or API. This skill supports GraphQL mutations for type assignment, allowing you to categorize tasks for better feature planning and tracking.

What is the best way to coordinate release planning across multiple GitHub issues?

The best way to coordinate release planning is to create epics and establish issue dependencies. This governs progress tracking by enforcing execution order across linked sub-issues within your project workflows.

Does this GitHub issue management approach work with existing project labels and workflows?

Yes, this approach integrates with existing project labels and workflows. It centralizes the governance of GitHub issues, allowing you to apply advanced features like dependencies without disrupting your current tracking setup.

How do I structure GitHub tasks for feature planning using sub-issues?

To structure GitHub tasks for feature planning, create a main issue with a clear description and link related tasks as sub-issues. Referencing planning guides like zoonk-issue-planning helps structure the work hierarchically.

Why use GraphQL mutations for GitHub issue dependencies instead of standard API calls?

GraphQL mutations are used for GitHub issue dependencies because they support advanced relationship assignments like type designation and sub-issue linking. This provides scalable governance beyond standard API calls.