convert-issue-to-discussion_skill

Overview

This skill automates converting a GitHub issue into a discussion using a headed agent-browser session when the gh CLI cannot perform the operation. It guides the user through opening the issue page, logging in if required, clicking the conversion controls, selecting a discussion category, and confirming the conversion. It expects agent-browser to be installed and the user to complete any GitHub login prompts in the visible browser window.

How this skill works

The skill opens the target issue URL in a visible (headed) browser so the user can sign in. It inspects page elements with agent-browser snapshot calls to find the "Convert to discussion" control, clicks it, then selects the appropriate discussion category from the conversion dialog and confirms. It uses agent-browser commands to wait for elements and to interact with buttons, comboboxes, and options.

When to use it

• You need to move an issue into Discussions but the gh CLI lacks direct support.
• You want to convert support questions into a Q&A discussion for better community response.
• You want to move feature requests into an Ideas discussion to spur design conversation.
• You need an assisted, repeatable browser workflow because repository permissions require interactive login.
• You plan to convert multiple issues and want to reuse the browser login state.

Best practices

• Open the issue URL with --headed so the browser shows and you can complete GitHub login.
• Take snapshots (agent-browser snapshot -i) to inspect element refs before clicking or selecting.
• Choose discussion categories intentionally: Q&A for support, Ideas for feature requests, General for announcements.
• Wait for the page elements to load (use agent-browser wait) before interacting to avoid missed clicks.
• Keep the browser open between conversions to reuse the login session for subsequent operations.

Example use cases

• Convert a reported bug that is actually a support question into a Q&A discussion.
• Move a feature request issue into the Ideas category to start a broader community design thread.
• Change an issue with long commentary into a General discussion to preserve conversation flow.
• Batch-convert several repository issues while staying signed in via the headed browser.
• Onboard contributors by converting low-value issues into show-and-tell discussions for examples.