convert-github-issue-to-discussion

Convert GitHub issues to discussions via a browser automation workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert GitHub issues to discussions using a browser-automation workflow, reducing manual steps and ensuring consistent categorization.

Core Features & Use Cases

  • Browser-based conversion: Open the issue in a headed browser, locate the Convert to discussion action, and perform the conversion.
  • Category selection: Choose an appropriate discussion category (Q&A, Ideas, General, Show and tell) to align with the issue intent.
  • Automation-ready workflow: Designed to be initiated on prompt, with prerequisites clearly stated (agent-browser installed and user login).

Quick Start

Convert a GitHub issue into a discussion by following the agent-browser workflow.

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 automate converting GitHub issues to discussions?

You can convert GitHub issues to discussions by using a browser automation workflow that opens the issue in a headed browser, locates the conversion action, and selects a discussion category.

Do I need agent-browser installed to convert GitHub issues to discussions?

Yes, agent-browser must be installed to run the conversion workflow. You also need to log in via a headed browser and have access to the relevant repository.

When should I convert GitHub issues to discussions instead of leaving them as issues?

Converting GitHub issues to discussions is useful for triage and project alignment when a conversation fits categories like Q&A, Ideas, General, or Show and tell better than an issue tracker.

What's the best way to ensure consistent categorization when migrating GitHub issues to discussions?

Using a browser-automation workflow ensures consistent categorization by automatically selecting appropriate discussion categories like Q&A, Ideas, General, or Show and tell during the migration.

Can I convert GitHub issues to discussions without manual steps in the browser?

The workflow initiates automatically on prompt but requires a headed browser for user login. This ensures secure access to the repository before the browser automation performs the conversion.