create-issue

Convert unstructured user reports into schema-valid GitHub issues for JellyRock.

37|2|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill create-issue-jellyrock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/create-issue
Command: npx skills add https://github.com/jellyrock/jellyrock --skill create-issue-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

User reports from Reddit, Discord, email, or other platforms are often unstructured, missing required fields, and hard to triage into actionable GitHub issues, leading to incomplete bug reports and wasted follow-up time for maintainers.

Core Features & Use Cases

  • Template-Aware Issue Drafting: Automatically classifies input into the correct JellyRock repository issue template (bug report, feature request, or enhancement) and fills required fields by extracting information from unstructured input.
  • Duplicate Detection: Searches existing open issues before filing to avoid duplicate reports, surfacing candidates for user review instead of auto-deciding.
  • Honest Gap Marking: Never fabricates missing required fields like Roku device model or JellyRock version, instead marking gaps explicitly for follow-up with the original reporter.
  • Use Case: A community manager pastes a Discord bug report about JellyRock crashing during playback; the skill automatically fills the bug report template, flags missing version and device info, checks for duplicates, and submits a properly labeled issue after user confirmation.

Quick Start

Paste an unstructured user bug report from Discord or Reddit into the create-issue skill to generate and submit a properly formatted, labeled GitHub issue for the JellyRock repository.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I convert unstructured Discord or Reddit bug reports into valid GitHub issues?

Converting unstructured user reports into valid GitHub issues is done by pasting freeform text into the workflow, which extracts required fields and classifies input into the correct repository-specific issue template.

How does duplicate detection work when filing GitHub issues from community reports?

Duplicate detection works by searching existing open GitHub issues before submission, surfacing candidate matches for user review instead of auto-deciding, ensuring no duplicate reports are filed in the triage workflow.

Can I use the gh CLI to auto-label and submit GitHub issues from freeform text?

Yes, you can use the gh CLI to apply auto-labels and submit GitHub issues, validating output against template schemas during submission after user confirmation.

What is the best way to triage feature requests and bug reports from email into GitHub?

The best way to triage feature requests and bug reports from email is to classify the unstructured input into the correct issue template, extract required fields, and submit a properly labeled GitHub issue after checking for duplicates.

What happens if a user bug report is missing required information like the software version?

When required information like the software version is missing, the workflow marks the gap explicitly for follow-up with the original reporter rather than fabricating the missing data.