mcpField
C
comet-github-idea-to-issue

comet-github-idea-to-issue

github.com/rpamisDevelopment3.2k117 installsUpdated today
Repository

About comet-github-idea-to-issue

A Comet skill for turning local observations into GitHub issue drafts, aimed at maintainers reporting bugs, feature ideas, or tasks. It checks the implementation, related issues and PRs, and repository templates; creating an issue requires explicit confirmation.

Key features

  1. 01Inspect implementation, tests, and documentation
  2. 02Search for duplicate issues and PRs
  3. 03Draft content using repository templates
  4. 04Separate evidence from unverified assumptions
  5. 05Create and verify issues after confirmation

Use cases

  1. 01Turn a local finding into a bug report
  2. 02Draft a templated issue from a feature idea
  3. 03Check whether a report duplicates an existing issue

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rpamis/comet --skill comet-github-idea-to-issue

After installing, type/comet-github-idea-to-issuein Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Comet 本地想法转 GitHub Issue

先读取 ../comet-github/references/maintainer-contract.md。起草阶段只读;创建 GitHub Issue 必须得到明确确认。

确定 Issue 内容

  1. 理解本地观察,检查当前实现、测试、Runtime 路径和相关文档。
  2. 按领域概念搜索已有 GitHub Issue 和 PR,判断这是重复问题、已有 Issue 的 follow-up,还是新报告。
  3. 选择最匹配的仓库模板:bug、feature、task 或 question。起草字段前先读取当前 YAML 模板。
  4. 区分用户可见问题和推测的实现原因。只有有助于复现或界定范围时才写入实现细节。

起草正文

生成以下内容:

  • 使用仓库模板前缀的简洁标题;
  • 受影响的 workflow、平台和版本/状态;
  • 当前行为与预期行为;
  • 复现步骤或触发该想法的用户流程;
  • 已有证据和疑似边界,未经验证的内容标注为假设;
  • 明确范围和非目标;
  • 可以独立检查的验收标准;
  • 相关 Issue/PR 链接和重复搜索说明。

Feature 需要先描述 workflow 问题和期望行为,再提出实现方案。Bug 需要在必要时保留准确命令、日志、版本和项目状态。

确认后再发布

先展示完整的标题、模板类型、标签和正文。得到确认后才能调用 gh issue create。创建后验证返回的 URL 和标题,并报告 Issue 编号。除非另行要求,不修改标签、不关闭相关 Issue,也不创建额外 ticket。

Comments

Markdown supported