Create GitHub Issue

VerifiedSafe

Creates a GitHub issue in the gittower/git-flow-next repository following project guidelines. Checks for existing duplicates, determines the issue type and labels, and formats the body using templates for bugs, enhancements, or features. Helps ensure consistent and well-structured issue reports.

Sby Skills Guide Bot
DevelopmentBeginner
1006/2/2026
Claude Code
#github#issue-tracking#project-workflow

Recommended for

Our review

Creates a structured GitHub issue in the gittower/git-flow-next repository following project guidelines.

Strengths

  • Automatically checks for duplicates before creating the issue.
  • Provides templates tailored to issue type (bug, enhancement, feature).
  • Integrates with MCP tools to interact directly with the GitHub API.

Limitations

  • Limited to the gittower/git-flow-next repository.
  • Requires MCP tools to be configured and available.
  • Templates are basic and may not cover all edge cases.
When to use it

Use this skill when you need to create a well-structured GitHub issue for the git-flow-next project, adhering to team conventions.

When not to use it

Do not use it for other repositories or when you need a custom issue format not covered by the provided templates.

Security analysis

Safe
Quality score90/100

The skill only uses read, search, and create-issue GitHub MCP tools. No shell execution, data exfiltration, or safety bypass. No risky instructions.

No concerns found

Examples

Report a bug
Create a bug issue: [bug] Git merge fails when feature branch has conflicts
Request a feature
Create a feature issue: [feature] Add support for rebase workflows
Enhancement request
Create an enhancement issue: [enhancement] Improve error messages in merge command

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