github-issue

Creates GitHub Issues following repository templates with sizing and sub-issue guidelines.

1|Updated Feb 16, 2025
One-click install
npx skills add https://github.com/yellow-seed/my-portfolio --skill github-issue-yellow-seed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue
Source: https://github.com/yellow-seed/my-portfolio/tree/main/.github/skills/github-issue
Command: npx skills add https://github.com/yellow-seed/my-portfolio --skill github-issue-yellow-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing well-structured GitHub Issues that follow a repository's issue templates and have appropriate scope is time-consuming and inconsistent. This Skill standardizes Issue creation by enforcing template compliance, proper task granularity, and clear acceptance criteria. ## Core Features & Use Cases - Template-Compliant Issue Creation: Generates Issues matching the repository's bug_report, feature_request, and todo templates with correct labels. - Granularity Guidance: Evaluates whether a task fits in a single PR (1-3 days of work) and splits oversized requests into multiple Issues. - Main/Sub-Issue Hierarchies: Structures large features as a main Issue with linked sub-issues tracked via task lists, where each sub-issue maps one-to-one with a PR. - Use Case: When asked to plan a user authentication feature, the Skill creates a main Issue describing the overall goal, then generates sub-issues for the database schema, API endpoints, middleware, and UI, each with acceptance criteria and cross-links. ## Quick Start Ask the AI to create a GitHub Issue for a bug report or feature request following the repository's issue 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 a GitHub Issue from a template?▼

Select the matching template type (bug report, feature request, or todo), fill in every required field such as reproduction steps or acceptance criteria, then create the Issue with the gh issue create command and the appropriate label.

How to split a large feature into multiple GitHub Issues?▼

Create a main Issue describing the overall goal, then add sub-issues as a task list where each sub-issue corresponds to one PR of roughly one to three days of work. Link sub-issues back to the parent and close them via PR descriptions using Closes #number.

What is the right size for a GitHub Issue?▼

An Issue should be completable in a single pull request, typically one to three days of work with a single responsibility and clear acceptance criteria. Split Issues that span multiple features, layers, or staged releases.

How do sub-issues relate to pull requests on GitHub?▼

Each sub-issue maps one-to-one with a pull request. Adding Closes #issue-number in the PR body automatically closes the sub-issue on merge, and the main Issue's task list checkbox updates to reflect progress.

When should I avoid splitting work into sub-issues?▼

Avoid splitting when tasks are too small, since excessive sub-issues increase management overhead. Only split when work exceeds a single PR's scope, and reconsider merging or re-splitting if the granularity proves wrong during implementation.