Create GitHub Issue

VerifiedSafe

Create a new GitHub issue for gittower/git-flow-next repository following project guidelines. Checks for duplicates and uses structured templates.

Sby Skills Guide Bot
DevelopmentBeginner
206/2/2026
Claude Code
#github#issue-tracking#project-management#git-flow

Recommended for

Our review

Creates a GitHub issue for the gittower/git-flow-next repository following predefined templates.

Strengths

  • Automatically checks for duplicates before creating
  • Provides structured templates per issue type
  • Applies appropriate labels

Limitations

  • Relies on the MCP GitHub tool for API access
  • Does not handle projects or milestones
  • Templates are specific to the git-flow-next repository
When to use it

When you need to report a bug, request a feature, or suggest an improvement for the git-flow-next project.

When not to use it

For issues outside the git-flow-next repository or when a custom template is needed.

Security analysis

Safe
Quality score90/100

The skill only uses read-only tools and GitHub API tools (create_issue, list_issues, search_issues) within a specific repository. No shell execution, network calls outside MCP, or destructive actions. The instructions are transparent and follow standard issue creation workflows.

No concerns found

Examples

Bug report for git-flow-next
Create a GitHub issue: bug - git-flow fails on Windows when path contains spaces
Feature request for git-flow-next
Create a GitHub issue for a new feature: Add support for custom branch naming conventions
Enhancement request with minimal info
Create a GitHub issue: enhancement - Improve error messages when git-flow commands are misused

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