---

name: github-issue-creator description: "将错误日志、截图、语音笔记和粗略的 bug 报告转化为清晰、开发者可用的 GitHub issue，包含复现步骤、影响和证据。" risk: unknown source: community date_added: "2026-02-27"

GitHub Issue 创建器

将混乱的输入（错误日志、语音笔记、截图）转化为清晰、可操作的 GitHub issue。

输出模板

## Summary
[问题的一行描述]

## Environment
- **Product/Service**: 
- **Region/Version**: 
- **Browser/OS**: (if relevant)

## Reproduction Steps
1. [Step]
2. [Step]
3. [Step]

## Expected Behavior
[应该发生什么]

## Actual Behavior
[实际发生了什么]

## Error Details
\`\`\`
[错误消息/代码（如适用）]
\`\`\`

## Visual Evidence
[附加截图/GIF 的引用]

## Impact
[严重程度: Critical/High/Medium/Low + 简要说明]

## Additional Context
[任何其他相关细节]

输出位置

将 issue 创建为 markdown 文件，放在仓库根目录的 /issues/ 目录中。使用命名约定：YYYY-MM-DD-short-description.md

指南

简洁明了：不要废话。每个词都应该增加价值。

从混乱中提取结构：语音听写和原始笔记中的事实往往埋藏在随意的语言中。把它们提取出来。

推断缺失的上下文：如果用户提到"同一个项目"或"仪表板"，使用对话或记忆中的上下文来填充具体信息。

占位敏感数据：对可能敏感的内容使用 [PROJECT_NAME]、[USER_ID] 等。

严重程度与影响匹配：

• Critical：服务宕机、数据丢失、安全问题
• High：主要功能损坏、无变通方案
• Medium：功能受损、存在变通方案
• Low：轻微不便、外观问题

图片/GIF 处理：内联引用附件。格式：!Description

示例

输入（语音听写）：

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

输出：

## Summary
Agent deployment fails silently - no error displayed, agent disappears from list

## Environment
- **Product/Service**: Azure AI Foundry
- **Region/Version**: westus2

## Reproduction Steps
1. Navigate to agent deployment
2. Configure and deploy agent
3. Observe workflow completes
4. Check agent list

## Expected Behavior
Agent appears in list with deployment status, errors shown if deployment fails

## Actual Behavior
Agent disappears from list. No error message. Requires page refresh and retry.

## Impact
**High** - Blocks agent deployment workflow, no feedback on failure cause

## Additional Context
Required 3 retry attempts before successful deployment

---

输入（错误粘贴）：

Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.

输出：

## Summary
403 PERMISSION_DENIED error when publishing to Teams channel

## Environment
- **Product/Service**: Teams Integration
- **Region/Version**: Production

## Reproduction Steps
1. Attempt to publish content to Teams channel
2. Observe 403 error

## Expected Behavior
Content publishes successfully (was working previously)

## Actual Behavior
PERMISSION_DENIED error with code 403

## Impact
**High** - Regression, was working yesterday, blocks Teams publishing workflow

限制

• 仅在任务明确匹配上述描述范围时使用此技能。
• 不要将输出视为环境特定验证、测试或专家审查的替代品。
• 如果缺少所需输入、权限、安全边界或成功标准，请停下来要求澄清。