Back to Details

github-issues

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GitHub Issues

GitHub Issue处理

Use the installed skill script directly:
bash
node "$SKILL_DIR/scripts/github-issues.mjs" <command> [options]
SKILL_DIR
is the directory containing this 
SKILL.md
.
直接使用已安装的skill脚本：
bash
node "$SKILL_DIR/scripts/github-issues.mjs" <command> [options]
SKILL_DIR
是包含此
SKILL.md
文件的目录。

Inputs

输入项

  • .env
    with: 
    • GITHUB_API_KEY=<token>
    • GITHUB_REPOSITORY=<owner/repo>
  • Target issue number, or use worklist mode when unspecified
  • 包含以下内容的
    .env
    文件： 
    • GITHUB_API_KEY=<token>
    • GITHUB_REPOSITORY=<owner/repo>
  • 目标Issue编号，未指定时使用工作列表模式

Steps

操作步骤

  1. Read issue details and comments: 
    • node "$SKILL_DIR/scripts/github-issues.mjs" read -n <issue-number> --comments
  2. Classify issue type:
    1. Code-change request
    2. Brainstorm/open discussion
    3. Irrelevant to this repository
  3. Execute by type:
    1. Code-change request:
      1. Create branch 
        issue-<number>-<topic>
        .
      2. Implement and validate changes.
      3. Commit and push branch.
      4. Post summary comment including commit ID.
      5. Close only when fully resolved.
    2. Brainstorm/open discussion:
      1. Post concise, constructive response grounded in repository context.
      2. Ask only unblocker questions when needed.
    3. Irrelevant issue:
      1. Post a short polite response.
      2. Keep response brief.
  4. Address one issue end-to-end per skill call.
  5. After completion, ask whether to continue with the next issue.
  1. 查看Issue详情及评论： 
    • node "$SKILL_DIR/scripts/github-issues.mjs" read -n <issue-number> --comments
  2. 分类Issue类型：
    1. 代码变更请求
    2. 头脑风暴/公开讨论
    3. 与当前仓库无关
  3. 按类型执行处理：
    1. 代码变更请求：
      1. 创建分支 
        issue-<number>-<topic>
        。
      2. 实现并验证变更内容。
      3. 提交并推送分支。
      4. 发布包含提交ID的总结评论。
      5. 仅在完全解决后关闭Issue。
    2. 头脑风暴/公开讨论：
      1. 基于仓库上下文发布简洁且有建设性的回复。
      2. 仅在需要时提出用于解决阻塞的问题。
    3. 无关Issue：
      1. 发布简短且礼貌的回复。
      2. 保持回复简洁。
  4. 每次调用skill时完整处理一个Issue。
  5. 处理完成后，询问是否继续处理下一个Issue。

CLI Reference

CLI参考

  • Work queue: 
    node "$SKILL_DIR/scripts/github-issues.mjs" worklist
  • List open issues: 
    node "$SKILL_DIR/scripts/github-issues.mjs" read -s open -l 20
  • Read one issue: 
    node "$SKILL_DIR/scripts/github-issues.mjs" read -n <issue-number>
  • Read issue + comments: 
    node "$SKILL_DIR/scripts/github-issues.mjs" read -n <issue-number> --comments
  • Add comment: 
    node "$SKILL_DIR/scripts/github-issues.mjs" comment -n <issue-number> -b "<text>"
  • Close issue: 
    node "$SKILL_DIR/scripts/github-issues.mjs" close -n <issue-number> -b "<resolution note>"
  • 工作队列：
    node "$SKILL_DIR/scripts/github-issues.mjs" worklist
  • 列出未关闭Issue：
    node "$SKILL_DIR/scripts/github-issues.mjs" read -s open -l 20
  • 查看单个Issue：
    node "$SKILL_DIR/scripts/github-issues.mjs" read -n <issue-number>
  • 查看Issue及评论：
    node "$SKILL_DIR/scripts/github-issues.mjs" read -n <issue-number> --comments
  • 添加评论：
    node "$SKILL_DIR/scripts/github-issues.mjs" comment -n <issue-number> -b "<text>"
  • 关闭Issue：
    node "$SKILL_DIR/scripts/github-issues.mjs" close -n <issue-number> -b "<resolution note>"

Conventions

约定规范

  • Keep comments concise, explicit, and status-oriented.
  • Include assumptions when proceeding with incomplete issue details.
  • Ask focused numbered follow-up questions only when required to unblock implementation.
  • 评论需简洁、明确且聚焦状态。
  • 若Issue信息不完整，处理时需说明假设前提。
  • 仅在需要解决实现阻塞时，提出针对性的编号跟进问题。