gh-issue

Create GitHub issues with repository-specific formatting and labels.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill gh-issue-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/gh-issue
Command: npx skills add https://github.com/gittower/git-flow-next --skill gh-issue-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create well-structured GitHub issues for the git-flow-next repository without having to remember project-specific reporting rules, labels, or posting conventions.

Core Features & Use Cases

  • Issue Drafting: Turns a short problem description into a repository-ready issue title and body.
  • Guideline Compliance: Follows the project's issue formatting rules by reading the repository guidelines before creating an issue.
  • Duplicate Checking: Searches existing issues to avoid submitting redundant reports or requests.
  • Label Selection: Applies the appropriate bug or enhancement label based on the issue type.
  • Use Case: A developer notices a bug in git-flow-next and wants to file it quickly with the correct template and no duplicate entries.

Quick Start

Use the gh-issue skill to create a new GitHub issue from this bug report and follow the repository guidelines.

Frequently Asked Questions about gh-issue

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

FAQPage Schema
How do I create a GitHub issue that follows repository-specific formatting rules?

To create a GitHub issue that follows repository-specific formatting rules, provide a short problem description and the skill drafts a compliant title and body by reading repository guidelines before submission.

How can I check for duplicate GitHub issues before submitting a new bug report?

Checking for duplicate GitHub issues before submitting a bug report is handled automatically by searching existing repository tickets to validate the new request, preventing redundant entries.

What is the correct way to label a GitHub enhancement request versus a bug report?

Labeling a GitHub enhancement request versus a bug report correctly requires classifying the issue type from your description, which then applies the appropriate enhancement or bug label during creation.

Do I need GitHub issue search tools to file a repository bug report?

Yes, GitHub issue search and creation tools are required to file a repository bug report, as they validate the ticket, perform duplicate checks, and submit the formatted issue correctly.

Can I turn a short problem description into a repository-ready GitHub issue?

Yes, you can turn a short problem description into a repository-ready GitHub issue by applying the skill to draft the title and body while enforcing formatting and labeling rules.