Back to Skills

open-issue

Create a GitHub issue. Use when the user wants to create an issue, open an issue, or report a bug/feature request.

2starsUpdated 4/3/2026

Security Assessment

Safe(100/100)
Security Score100/100

About open-issue

The 'open-issue' skill allows users to create GitHub issues seamlessly through the use of the 'gh issue create' command. This skill simplifies the process of reporting bugs, submitting feature requests, or opening general issues on GitHub by automating the creation of the issue. It ensures that all the necessary details are included while minimizing manual input and the potential for errors. This skill is particularly useful for software development teams or open-source contributors who regularly interact with GitHub repositories and need to streamline the issue creation process.

The skill comes with a set of rules designed to make the issue creation process as efficient as possible. It leverages heredoc syntax to prevent shell escaping issues, and the body of the issue is structured using markdown headers for easy readability. The skill supports adding labels like 'bug', 'enhancement', or 'documentation' when the issue type is clear. It also encourages users to suggest creating a new label if none fit the issue, ensuring better organization within GitHub repositories. With a focus on simplicity and utility, 'open-issue' ensures users can focus on providing the right information while leaving the issue creation details to the tool.

This skill is targeted towards software developers, open-source contributors, and teams who regularly need to report issues on GitHub. It is beneficial for anyone who needs to track bugs, suggest new features, or document improvements. Whether for internal project management or external community engagement, this skill simplifies and automates the process of managing GitHub issues, reducing friction and boosting productivity.

FAQ

How do I create a GitHub issue using this skill?

You can create a GitHub issue by using the 'gh issue create' command. Make sure to provide a clear issue description and structure the body with markdown headers like '## Summary' and '## Details'.

What should I do if I cannot find a suitable label for my issue?

If no existing label fits the issue, it is recommended to suggest creating a new label before proceeding with issue creation.

Can I use this skill to automatically assign the issue to someone?

The current functionality of this skill does not include issue assignment. The focus is on creating and categorizing the issue with proper details and labels.

Are there any restrictions on the formatting of the issue body?

The issue body should be structured using markdown headers (e.g., '## Summary', '## Details'). It is also important to use heredoc syntax for the '--body' parameter to avoid shell escaping issues.

Is this skill compatible with all GitHub repositories?

Yes, this skill works with any GitHub repository where the 'gh' CLI tool is available and properly configured.

Install open-issue

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

sakuro/dotfiles