comet-github-idea-to-issue

Converts local Comet observations and improvement ideas into structured GitHub Issue drafts.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-github-idea-to-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-github-idea-to-issue
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-github-idea-to-issue
Command: npx skills add https://github.com/rpamis/comet --skill comet-github-idea-to-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning local code investigations, observed regressions, or improvement ideas into well-formed GitHub Issues is tedious and error-prone. This Skill structures that process so drafts follow the repository's issue templates, avoid duplicates, and only get published after explicit confirmation.

Core Features & Use Cases

  • Duplicate Detection: Searches existing GitHub Issues and PRs by domain concept to determine whether an observation is a duplicate, a follow-up, or a new report.
  • Template-Aligned Drafting: Selects the matching repository template (bug, feature, task, or question) and drafts title, affected workflow, reproduction steps, evidence, scope, and acceptance criteria.
  • Confirmation-Gated Publishing: Shows the full title, template type, labels, and body for review, and only runs gh issue create after explicit user confirmation.
  • Use Case: While debugging the Comet runtime you notice a regression in a workflow path. Use this Skill to verify it is not already reported, draft a bug Issue with reproduction steps and version details, and publish it after your approval.

Quick Start

Use the comet-github-idea-to-issue skill to turn my local findings about the workflow regression into a focused GitHub Issue draft.

Frequently Asked Questions about comet-github-idea-to-issue

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

FAQPage Schema
How do I turn a local code investigation into a GitHub Issue?

Describe your local observation or regression to the Skill, which inspects the current implementation, tests, and runtime paths, then drafts a template-compliant Issue with reproduction steps and acceptance criteria. The Issue is only created after you confirm the full draft.

How does the Skill avoid creating duplicate GitHub Issues?

It searches existing GitHub Issues and PRs by domain concept before drafting, then classifies your observation as a duplicate, a follow-up to an existing Issue, or a genuinely new report, including the duplicate search notes in the draft.

Which GitHub Issue templates does it support?

It selects the most appropriate repository template among bug, feature, task, and question, reading the current YAML template before drafting fields. Bugs keep exact commands, logs, and versions; features describe the workflow problem before proposing an implementation.

Does the Skill create GitHub Issues automatically?

No. Drafting is read-only, and the Skill has disable-model-invocation enabled. It presents the complete title, template type, labels, and body first, and only runs gh issue create after your explicit confirmation.

What are the limitations of this Issue drafting workflow?

It does not modify labels, close related Issues, or create extra tickets unless explicitly requested. Unverified hypotheses are marked as assumptions, and it depends on the GitHub CLI (gh) being available for the final creation step.