convert-github-issue-to-discussion

Convert GitHub issues into discussions using agent-browser automation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts GitHub issues into discussions using a browser automation workflow when the GitHub CLI cannot perform the action.

Core Features & Use Cases

  • Automates the conversion of issues to discussions via a headed browser using agent-browser.
  • Requires user login when prompted and supports selecting a discussion category (General, Q&A, Ideas).
  • Useful for teams migrating issue discussions to a structured discussion format for collaboration and visibility.

Quick Start

Open the GitHub issue page in a headed browser with agent-browser and follow the prompts to convert it into a discussion.

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 into discussions when the CLI fails?▼

To convert GitHub issues into discussions when the CLI fails, you can use browser automation to navigate the issue page, trigger the conversion, select a category, and confirm the action.

What is the best way to automate migrating GitHub issues to discussions?▼

Automating GitHub issue migration to discussions is best handled by a headed browser session that logs into your account, navigates to the target issue, and performs the structured conversion workflow.

Do I need a headed browser session to transform GitHub issues into discussions?▼

Yes, transforming GitHub issues into discussions requires a headed browser session because it necessitates user login to navigate the repository and execute the category selection and confirmation steps.

Can I select a discussion category like Q&A or Ideas when converting issues?▼

Yes, when converting issues into discussions, the workflow supports selecting a specific category such as General, Q&A, or Ideas to structure the captured decisions and questions effectively.

Why does converting GitHub issues to discussions require a browser instead of the CLI?▼

Converting GitHub issues to discussions requires browser automation because the GitHub CLI lacks the native capability to perform this specific repository transformation, necessitating a headed browser workflow.

When should I move a GitHub issue to the discussions section?▼

You should move a GitHub issue to discussions when it functions as a question, idea, or decision capture, benefiting from a structured collaboration format rather than a tracked issue.