ginee-promote-discussion

Promote a GitHub discussion into a labeled issue with a draft for approval.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-promote-discussion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ginee-promote-discussion
Source: https://github.com/kostiantyn-matsebora/ginee/tree/main/core/skills/ginee-promote-discussion
Command: npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-promote-discussion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates promoting a GitHub discussion into a labeled issue within the ginee framework, enabling you to convert conversations into tracked work.

Core Features & Use Cases

  • Draft an issue from a discussion using the appropriate templates (feature/bug) and preserve a link to the source discussion.
  • Surface a draft for user approval and create the issue with framework or primary target, then comment back on the discussion with the result.
  • Support framework-target routing when a framework is specified, and maintain traceability between the discussion and the created issue.

Quick Start

Promote discussion #N to an issue, optionally targeting a framework.

Frequently Asked Questions about ginee-promote-discussion

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

FAQPage Schema
How do I promote a GitHub discussion into a tracked issue?

Promoting a GitHub discussion into an issue involves loading the discussion content and drafting a labeled issue using feature or bug templates. The system surfaces the draft for your approval before creating the issue and linking it back to the original conversation.

Can I target a specific framework when converting a discussion to an issue?

Yes, you can target a specific framework when converting a discussion to an issue. The ginee workflow supports framework-target routing when a framework is specified, ensuring the issue is created in the correct target repository with proper labels.

How does discussion-to-issue traceability work in automated workflows?

Discussion-to-issue traceability is maintained by linking the created issue back to the original conversation. After the issue is created on the target repository, the automation comments on the source discussion with the result, preserving the connection.

What is the best way to draft an issue from a GitHub discussion?

The best way to draft an issue from a GitHub discussion is using template-driven automation. The ginee workflow loads the discussion and drafts an issue using the appropriate feature or bug template, surfacing it for user approval before creating the issue with proper labels.

Do I need to approve the issue draft before it is created from a discussion?

Yes, you need to approve the issue draft before it is created from a discussion. The automation surfaces the drafted issue for user approval, ensuring you can review the generated content and labels before the issue is created on the target repository.