gh:issue-create

Creates a GitHub issue from the current chat via gh.

Updated May 31, 2025
One-click install
npx skills add https://github.com/dEitY719/dotfiles --skill gh-issue-create-deity719
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh:issue-create
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/gh-issue-create
Command: npx skills add https://github.com/dEitY719/dotfiles --skill gh-issue-create-deity719

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill converts an ongoing chat into a well-structured GitHub issue in the target repository by classifying the conversation, drafting a detailed, template-backed body, and creating it via gh without requiring confirmation.

Core Features & Use Cases

  • Detects and validates the git repo context and resolves the target owner/repo from the chosen remote.
  • Classifies the conversation into feature / bug / misc to determine the issue title and structure.
  • Drafts a structured issue body using templates from references, preserving decisions and dialogue for future PRs or posts.
  • Creates the issue with gh issue create using a temporary file to prevent shell escaping issues.
  • Prints only the resulting issue number and URL.
  • Supports an optional remote argument (e.g., /gh-issue-create upstream) to target a non-origin repository.

Quick Start

Run /gh-issue-create to generate the issue in the current repo using the default origin remote, or specify a remote like /gh-issue-create upstream to target another repo.

Frequently Asked Questions about gh:issue-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub issue from a chat conversation automatically?

To create a GitHub issue from a chat, the skill classifies the conversation into a feature, bug, or misc category, drafts a structured template-based body, and executes gh issue create within the target repository.

How do I generate a GitHub issue from a discussion without manual formatting?

Generating a GitHub issue from a discussion is handled by resolving the git remote to an owner/repo, drafting the conversation into a template, and writing it to a temporary file to prevent shell escaping issues before creation.

Can I target a non-origin repository when creating GitHub issues from a chat?

Yes, you can target a non-origin repository by providing an optional remote argument, allowing the issue creation process to resolve and write to a different specified remote instead of the default origin.

Does the GitHub issue creation workflow require confirmation prompts?

No, the GitHub issue creation workflow performs no confirmation prompts, automatically classifying the dialogue, drafting the body, and outputting only the resulting issue number and URL directly.

How does conversation classification affect GitHub issue generation?

Conversation classification determines the GitHub issue generation structure by categorizing the chat as a feature, bug, or misc, which directly shapes the resulting template-based title and body content.

What is the best way to preserve chat decisions for future GitHub pull requests?

The best way to preserve chat decisions is to draft a structured GitHub issue body using templates, capturing the dialogue context for future pull requests or posts before creating the issue.