Back to Details

github-issue-creator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GitHub Issue Creator

GitHub Issue Creator

Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.
将杂乱的输入内容（错误日志、语音笔记、截图）转换为清晰、可执行的GitHub Issue。

Output Template

输出模板

markdown
undefined
markdown
undefined

Summary

摘要

[One-line description of the issue]
[问题的单行描述]

Environment

环境

  • Product/Service:
  • Region/Version:
  • Browser/OS: (if relevant)
  • 产品/服务:
  • 区域/版本:
  • 浏览器/操作系统: （如适用）

Reproduction Steps

复现步骤

  1. [Step]
  2. [Step]
  3. [Step]
  1. [步骤]
  2. [步骤]
  3. [步骤]

Expected Behavior

预期行为

[What should happen]
[应该发生的情况]

Actual Behavior

实际行为

[What actually happens]
[实际发生的情况]

Error Details

错误详情

[Error message/code if applicable]
[适用的错误消息/代码]

Visual Evidence

可视化证据

[Reference to attached screenshots/GIFs]
[附件截图/GIF的引用]

Impact

影响

[Severity: Critical/High/Medium/Low + brief explanation]
[严重级别：Critical/High/Medium/Low + 简要说明]

Additional Context

额外上下文

[Any other relevant details]
undefined
[其他相关细节]
undefined

Output Location

输出位置

Create issues as markdown files in 
/issues/
directory at the repo root. Use naming convention: 
YYYY-MM-DD-short-description.md
将生成的Issue以Markdown文件形式保存到仓库根目录的
/issues/
文件夹中。命名规则：
YYYY-MM-DD-short-description.md

Guidelines

指导原则

Be crisp: No fluff. Every word should add value.
Extract structure from chaos: Voice dictation and raw notes often contain the facts buried in casual language. Pull them out.
Infer missing context: If user mentions "same project" or "the dashboard", use context from conversation or memory to fill in specifics.
Placeholder sensitive data: Use 
[PROJECT_NAME]
, 
[USER_ID]
, etc. for anything that might be sensitive.
Match severity to impact:
  • Critical: Service down, data loss, security issue
  • High: Major feature broken, no workaround
  • Medium: Feature impaired, workaround exists
  • Low: Minor inconvenience, cosmetic
Image/GIF handling: Reference attachments inline. Format: 
![Description](attachment-name.png)
简洁明了：避免冗余，每一个表述都要有价值。
从杂乱中提取结构：语音听写和原始笔记中的关键信息常隐藏在口语化表述中，需要将其提炼出来。
推断缺失的上下文：如果用户提到“同一个项目”或“该仪表板”，请使用对话或记忆中的上下文信息补充具体内容。
敏感数据占位：对于可能涉及敏感信息的内容，使用
[PROJECT_NAME]
、
[USER_ID]
等占位符代替。
根据影响程度匹配严重级别：
  • Critical: 服务中断、数据丢失、安全问题
  • High: 主要功能故障，无替代方案
  • Medium: 功能受损，但存在替代方案
  • Low: 轻微不便，仅影响外观
图片/GIF处理：在正文中引用附件。格式：
![描述](附件名称.png)

Examples

示例

Input (voice dictation):
so I was trying to deploy the agent and it just failed silently no error nothing the workflow ran but then poof gone from the list had to refresh and try again three times
Output:
markdown
undefined
输入（语音听写）:
我刚才尝试部署Agent，但它直接静默失败了，没有任何错误提示。工作流运行了，但之后Agent就从列表里消失了，我不得不刷新页面重试了三次。
输出:
markdown
undefined

Summary

摘要

Agent deployment fails silently - no error displayed, agent disappears from list
Agent部署静默失败 - 无错误提示，Agent从列表中消失

Environment

环境

  • Product/Service: Azure AI Foundry
  • Region/Version: westus2
  • 产品/服务: Azure AI Foundry
  • 区域/版本: westus2

Reproduction Steps

复现步骤

  1. Navigate to agent deployment
  2. Configure and deploy agent
  3. Observe workflow completes
  4. Check agent list
  1. 进入Agent部署页面
  2. 配置并部署Agent
  3. 观察工作流完成
  4. 查看Agent列表

Expected Behavior

预期行为

Agent appears in list with deployment status, errors shown if deployment fails
Agent应出现在列表中并显示部署状态，若部署失败则展示错误信息

Actual Behavior

实际行为

Agent disappears from list. No error message. Requires page refresh and retry.
Agent从列表中消失，无错误提示，需刷新页面并重试

Impact

影响

High - Blocks agent deployment workflow, no feedback on failure cause
高 - 阻碍Agent部署工作流，无法获取失败原因的反馈

Additional Context

额外上下文

Required 3 retry attempts before successful deployment

---

**Input (error paste)**:
> Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.

**Output**:
```markdown
重试3次后才部署成功

---

**输入（错误粘贴）**:
> 错误：发布到Teams频道时出现PERMISSION_DENIED。代码：403。昨天还能正常工作。

**输出**:
```markdown

Summary

摘要

403 PERMISSION_DENIED error when publishing to Teams channel
发布到Teams频道时出现403 PERMISSION_DENIED错误

Environment

环境

  • Product/Service: Copilot Studio → Teams integration
  • Region/Version: [REGION]
  • 产品/服务: Copilot Studio → Teams集成
  • 区域/版本: [REGION]

Reproduction Steps

复现步骤

  1. Configure agent for Teams channel
  2. Attempt to publish
  1. 为Teams频道配置Agent
  2. 尝试发布

Expected Behavior

预期行为

Agent publishes successfully to Teams channel
Agent成功发布到Teams频道

Actual Behavior

实际行为

Returns 
PERMISSION_DENIED
with code 403
返回
PERMISSION_DENIED
错误，代码403

Error Details

错误详情

Error: PERMISSION_DENIED
Code: 403
Error: PERMISSION_DENIED
Code: 403

Impact

影响

High - Blocks Teams integration, regression from previous working state
高 - 阻碍Teams集成，与之前正常状态相比出现功能退化

Additional Context

额外上下文

Was working yesterday - possible permission/config change or service regression
undefined
昨天还能正常工作 - 可能是权限/配置变更或服务退化导致
undefined