github-issue-creator
从原始笔记创建GitHub问题
不再为非结构化的错误报告而烦恼。将语音笔记、错误日志和混乱的描述转化为专业的GitHub问题，让开发人员能够真正使用。
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“github-issue-creator”。 Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.
预期结果:
- Summary: 403 PERMISSION_DENIED error when publishing to Teams channel
- Environment: Copilot Studio Teams integration
- Expected: Agent publishes successfully to Teams channel
- Actual: Returns PERMISSION_DENIED with code 403
- Impact: High - Blocks Teams integration, regression from previous working state
正在使用“github-issue-creator”。 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
- Reproduction: Deploy agent, observe workflow completes, check agent list
- Expected: Agent appears in list with deployment status
- Actual: Agent disappears from list with no error message
- Impact: High - Blocks agent deployment workflow, no feedback on failure cause
安全审计
安全Static analyzer flagged 21 patterns as potential security issues, but all are false positives. The SKILL.md file contains only markdown documentation and prompt templates - no executable code. Backtick characters are used for markdown code blocks and inline code formatting, not shell command execution. No cryptographic functions or external command execution present.
质量评分
你能构建什么
快速记录缺陷
在重现问题时口述缺陷细节，然后立即将它们格式化为规范的GitHub问题。
错误日志分析
粘贴原始错误消息和堆栈跟踪，生成格式规范的结构化问题报告。
事件响应
通过描述发生的情况快速记录生产事件，然后生成正式的问题报告以便跟踪。
试试这些提示
I got this error: [paste error message]. Create a GitHub issue for this bug.
Convert this voice note into a GitHub issue: [paste transcribed voice message describing a bug]
Create a GitHub issue from this incident: Product: [name], Error: [details], Steps: [what you did], Expected: [what should happen], Impact: [who is affected]
Document this regression as a GitHub issue: Feature [name] was working [when]. Now [current behavior]. Error: [any error messages]. This blocks [workflow].
最佳实践
- Include specific error codes and messages in the Error Details section for faster debugging
- Clearly separate expected vs actual behavior to help developers understand the gap
- Assign severity levels honestly based on user impact, not personal frustration
避免
- Vague descriptions like it does not work without specific details about what is broken
- Mixing multiple unrelated bugs in one issue - create separate issues instead
- Speculating about root causes in the issue body instead of sticking to observed facts