convert-github-issue-to-discussion

Convert GitHub issues to discussions via headed browser automation.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/rokkay/dotfiles-macos --skill convert-github-issue-to-discussion-rokkay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convert-github-issue-to-discussion
Source: https://github.com/rokkay/dotfiles-macos/tree/main/config/claude/skills/convert-github-issue-to-discussion
Command: npx skills add https://github.com/rokkay/dotfiles-macos --skill convert-github-issue-to-discussion-rokkay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams migrate GitHub issues into discussions by automating the browser-driven conversion flow, keeping conversations centralized and actionable.

Core Features & Use Cases

  • Automates end-to-end conversion: login in headed mode, navigate to the issue, click Convert to discussion, select a category, and confirm.
  • Provides prompts and guidance when login is required or elements are not found, reducing manual intervention.
  • Use Case: convert support or feature-requests issues into discussions to gather broader input and feedback.

Quick Start

Open a headed browser session and instruct the agent to convert a GitHub issue to a discussion following the on-screen prompts.

Frequently Asked Questions about convert-github-issue-to-discussion

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

FAQPage Schema
How do I convert GitHub issues to discussions using browser automation?

To convert GitHub issues to discussions, browser automation logs into GitHub in headed mode, navigates to the issue, clicks 'Convert to discussion', selects a category, and confirms the conversion automatically.

Why convert GitHub issues into discussions instead of keeping them open?

Converting GitHub issues into discussions centralizes conversations for support or feature requests, gathering broader input and feedback while automating the migration flow to keep actionable items separate.

Do I need agent-browser installed to automate GitHub issue conversion?

Yes, agent-browser must be installed to automate GitHub issue conversion. The deterministic workflow requires a headed browser session and user login to interact with GitHub's UI elements properly.

Can I convert GitHub issues to discussions without logging into a headed browser?

No, converting GitHub issues to discussions requires user login in headed browser mode. The automation needs an active visual session to navigate pages, select discussion categories, and confirm conversions.

What happens if the GitHub discussion conversion elements are not found during automation?

When GitHub discussion conversion elements are not found, the automation provides prompts and guidance to reduce manual intervention, helping the user navigate login requirements or missing UI elements.

Is there a way to select a specific category when converting a GitHub issue to a discussion?

Yes, when converting a GitHub issue to a discussion, the automation workflow supports selecting a specific discussion category before confirming the conversion through the browser interface.