github-issue

Create focused GitHub issues or epics with sub-issues via GraphQL.

3|1|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/NodeSentinel/beacon-chain-validators-monitor --skill github-issue-nodesentinel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue
Source: https://github.com/NodeSentinel/beacon-chain-validators-monitor/tree/main/.claude/skills/github-issue
Command: npx skills add https://github.com/NodeSentinel/beacon-chain-validators-monitor --skill github-issue-nodesentinel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create focused, self-contained GitHub issues that external contributors can implement without additional context.

Core Features & Use Cases

  • Decision-flow to determine whether to create a single issue or an epic with sub-issues
  • Single-script workflow that batches epic and sub-issues creation via GraphQL
  • Clear workflow for reviewing, labeling, and linking issues to keep projects organized

Quick Start

Draft the appropriate GitHub issue or epic with sub-issues based on a user request.

Frequently Asked Questions about github-issue

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

FAQPage Schema
How do I create focused GitHub issues for external contributors?

Create focused GitHub issues for external contributors by using a deterministic workflow that breaks work into self-contained tasks or epics. This ensures contributors can implement issues with minimal context. The workflow applies decision guidance and labeling rules to keep projects organized.

When should I create a single GitHub issue versus an epic with sub-issues?

You should create a single GitHub issue versus an epic with sub-issues by following the built-in decision flow. This flow evaluates the work breakdown structure to determine if a task is self-contained or requires linked sub-issues. It applies labeling rules to keep projects organized.

Can I automate GitHub issue creation using GraphQL?

You can automate GitHub issue creation using GraphQL through a single-script workflow that batches epic and sub-issue creation. This reliable creation method optionally links issues together. It applies a deterministic workflow to generate focused, self-contained issues.

What is the best way to break down epics into sub-issues on GitHub?

The best way to break down epics into sub-issues on GitHub is using a single-script workflow that creates and optionally links them via GraphQL. This approach generates self-contained issues that external contributors can implement without additional context.

Does this GitHub issue automation workflow support labeling and linking?

This GitHub issue automation workflow supports labeling and linking through a clear, deterministic process. It applies specific labeling rules and optionally links sub-issues to epics during creation. This keeps your projects organized and issues self-contained.