open-issue

Convert conversation context into structured GitHub issues with tags and prefixes.

1|2|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill open-issue-madrid1011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-issue
Source: https://github.com/MAdrid1011/Zircon-VLIW/tree/main/.claude/skills/open-issue
Command: npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill open-issue-madrid1011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create GitHub issues from conversation context with proper formatting and tag selection. The AI agent analyzes the conversation, extracts issue details, and confirms with the user before creating the issue.

Core Features & Use Cases

  • Converts conversational context into well-structured GitHub issues with consistent prefixes and tags.
  • Supports tagging via docs/git-msg-tags.md and proper prefixing for plan and non-plan issues.
  • Provides a configurable workflow with optional inputs (--auto, --update) to streamline issue creation and updates.
  • Follows a defined workflow: parse arguments, analyze context, select tags, draft issue content, and confirm before creation.

Quick Start

Provide the issue context and run the tool to draft a GitHub issue for review.

Frequently Asked Questions about open-issue

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

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

To create a well-tagged GitHub issue from conversation context, this tool analyzes discussions, extracts relevant details, selects tags via docs/git-msg-tags.md, and drafts a structured issue body for your confirmation before creation.

Can I use conversation context to generate planning issues on GitHub?

Yes, you can generate planning issues on GitHub from conversation context. The tool supports optional plan-generation flows and applies appropriate prefixes to distinguish planning issues from standard bug reports or feature requests.

What is the best way to structure bug reports and feature requests for GitHub?

The best way to structure bug reports and feature requests is using a standardized format. This tool constructs a complete issue body containing Description, Steps to Reproduce, and Proposed Solution sections, ensuring consistent formatting and tagging.

Does this issue creation workflow support automatic updates to existing GitHub issues?

Yes, the issue creation workflow supports automatic updates to existing GitHub issues. By using the --auto and --update flags, you can streamline issue creation and updates without manual formatting.

How are tags selected when converting conversations into GitHub issues?

Tags are selected by referencing and validating definitions in docs/git-msg-tags.md. The tool analyzes conversation context to determine appropriate tags, formats titles with proper prefixes, and applies them to the drafted GitHub issue.

Do I need to manually format titles and prefixes for GitHub planning issues?

No, you do not need to manually format titles and prefixes for GitHub planning issues. The tool automatically handles prefixing for both plan and non-plan issues, ensuring title formatting consistency across your repository.