Create GitHub Issue

VerifiedSafe

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

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

Recommended for

Our review

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

Strengths

  • Automatically structures the issue body based on type (bug, enhancement, feature)
  • Checks for duplicate issues before creation
  • Applies appropriate labels
  • Generates clear, imperative titles

Limitations

  • Only works with the gittower/git-flow-next repository
  • Requires the GitHub MCP tool to be available
  • Does not handle attachments or issue assignments
When to use it

Use when you need to quickly create a well-formatted issue from the command line.

When not to use it

Avoid if you need to attach files, assign multiple people, or follow a custom workflow outside the provided templates.

Security analysis

Safe
Quality score85/100

The skill only uses safe GitHub API tools for searching and creating issues, with no execution of arbitrary commands or network calls beyond GitHub's API. No data exfiltration or destructive actions.

No concerns found

Examples

Report a bug
Create a GitHub issue for a bug: the login button does nothing when clicked on Firefox.
Request a feature
Create a GitHub issue for a feature: add dark mode support to the dashboard.
Enhance existing functionality
Create a GitHub issue for an enhancement: improve the search filter to allow date range selection.

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