Create GitHub Issue

VerifiedSafe

Create a new GitHub issue for gittower/git-flow-next repository following project guidelines. Includes duplicate checking and structured templates.

Sby Skills Guide Bot
DevelopmentBeginner
206/2/2026
Claude Code
#github-issues#issue-tracking#project-management#bug-reporting

Recommended for

Our review

Creates a structured GitHub issue for a specific repository, with duplicate checking and type selection.

Strengths

  • Generates well-formatted issues using appropriate templates (bug, enhancement, feature)
  • Automatically checks for duplicates before creation
  • Uses proper labels and imperative mood for titles

Limitations

  • Tied to the specific gittower/git-flow-next repository
  • Only supports the defined types (bug, enhancement, feature, documentation)
  • Does not handle updates or closing of issues
When to use it

Use this skill to quickly and consistently create GitHub issues for the git-flow-next project.

When not to use it

Do not use it for other repositories or when you need to create issues without a fixed template.

Security analysis

Safe
Quality score88/100

The skill solely uses GitHub read, search, and issue creation operations; it does not execute arbitrary commands, exfiltrate data, or perform destructive actions.

No concerns found

Examples

Report a bug
Create a bug issue: the login button doesn't respond on mobile view.
Request a feature
Create a feature request to add dark mode support.
Enhancement suggestion
Create an enhancement issue to improve search performance for large repositories.

name: gh-issue description: Create a GitHub issue following project guidelines argument-hint: <title or description> allowed-tools: Read, Grep, Glob, mcp__github__create_issue, mcp__github__list_issues, mcp__github__search_issues

Create GitHub Issue

Create a new GitHub issue for the gittower/git-flow-next repository following project guidelines.

Instructions

  1. Gather Information

    • If $ARGUMENTS is provided, use it as the issue title/description
    • If no arguments, ask the user for:
      • Issue type (bug, enhancement, feature)
      • Brief description of the issue
  2. Check for Duplicates

    • Search existing issues for similar topics
    • If potential duplicates found, show them to the user and ask to confirm creation
  3. Determine Issue Type and Labels

    • bug - Something isn't working
    • enhancement - Improvement to existing feature
    • feature - New feature request
    • documentation - Documentation improvements
  4. Create the Issue

    • Use clear, descriptive title (imperative mood: "Add...", "Fix...", "Update...")
    • Structure the body with appropriate sections based on type

Issue Body Templates

Bug Report

## Description
<Clear description of the bug>

## Steps to Reproduce
1.
2.
3.

## Expected Behavior
<What should happen>

## Actual Behavior
<What actually happens>

## Environment
- OS:
- Git version:
- git-flow-next version:

Enhancement/Feature

## Description
<Clear description of the enhancement/feature>

## Motivation
<Why is this needed? What problem does it solve?>

## Proposed Solution
<How should this work?>

## Alternatives Considered
<Other approaches considered, if any>
  1. Report Result
    • Show the created issue URL
    • Suggest next step: /analyze-issue <number> to start working on it
Related skills