What kind of structure does the generated issue have?

Issues are divided into three main sections: 'What & Why' for high-level summaries, 'Context & Discussion' for technical details and decisions, and an 'Implementation Plan' for actionable next steps.

Do I need the GitHub CLI installed for this skill to work?

Yes, this skill requires the GitHub CLI (gh) to be installed and authenticated on your local system to interact with your repositories.

Can I add labels or assignees to the issues created?

The skill can automatically add relevant labels (like bug or feature) based on context and will assign users if explicitly requested in the conversation.

How does the skill know which repository to use?

The skill runs a check for a GitHub remote in your current directory. If it cannot find one, it will prompt you to specify the repository manually.

GitHub Issue Creator

Name: GitHub Issue Creator
Author: Olshansk

byOlshansk

•

Collaboration Tools

Creates structured, professional GitHub issues from conversation context using the GitHub CLI.

The GitHub Issue Creator skill automates the transition from brainstorming to project management by synthesizing technical conversations into detailed GitHub issues. It leverages the GitHub CLI (gh) to generate well-organized issues that include context summaries, technical constraints, decision logs, and actionable implementation plans. This skill is essential for developers who want to maintain high-quality documentation and project tracking without disrupting their terminal-based AI development workflow.

Key Features

01Support for markdown formatting, including tables, code blocks, and collapsible sections

02Integration with GitHub CLI for seamless issue creation

03Automatic repository detection and remote verification

04Automatic synthesis of chat history into structured issue bodies

05Standardized templates including 'What & Why' and 'Implementation Plan' sections

066 GitHub stars

Use Cases

01Documenting technical debt and architectural decisions discussed with Claude

02Converting a complex debugging session into a formal bug report with reproduction steps

03Formalizing a feature request discussion into a technical specification for team review

Key Features

01Support for markdown formatting, including tables, code blocks, and collapsible sections

02Integration with GitHub CLI for seamless issue creation

03Automatic repository detection and remote verification

04Automatic synthesis of chat history into structured issue bodies

05Standardized templates including 'What & Why' and 'Implementation Plan' sections

066 GitHub stars

Use Cases

01Documenting technical debt and architectural decisions discussed with Claude

02Converting a complex debugging session into a formal bug report with reproduction steps

03Formalizing a feature request discussion into a technical specification for team review