Github Issue Creator

1---
2name: github-issue-creator
3description: Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.
4---
5 
6# GitHub Issue Creator
7 
8Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.
9 
10## Output Template
11 
12```markdown
13## Summary
14[One-line description of the issue]
15 
16## Environment
17- **Product/Service**: 
18- **Region/Version**: 
19- **Browser/OS**: (if relevant)
20 
21## Reproduction Steps
221. [Step]
232. [Step]
243. [Step]
25 
26## Expected Behavior
27[What should happen]
28 
29## Actual Behavior
30[What actually happens]
31 
32## Error Details
33```
34[Error message/code if applicable]
35```
36 
37## Visual Evidence
38[Reference to attached screenshots/GIFs]
39 
40## Impact
41[Severity: Critical/High/Medium/Low + brief explanation]
42 
43## Additional Context
44[Any other relevant details]
45```
46 
47## Output Location
48 
49**Create issues as markdown files** in `/issues/` directory at the repo root. Use naming convention: `YYYY-MM-DD-short-description.md`
50 
51## Guidelines
52 
53**Be crisp**: No fluff. Every word should add value.
54 
55**Extract structure from chaos**: Voice dictation and raw notes often contain the facts buried in casual language. Pull them out.
56 
57**Infer missing context**: If user mentions "same project" or "the dashboard", use context from conversation or memory to fill in specifics.
58 
59**Placeholder sensitive data**: Use `[PROJECT_NAME]`, `[USER_ID]`, etc. for anything that might be sensitive.
60 
61**Match severity to impact**:
62- Critical: Service down, data loss, security issue
63- High: Major feature broken, no workaround
64- Medium: Feature impaired, workaround exists
65- Low: Minor inconvenience, cosmetic
66 
67**Image/GIF handling**: Reference attachments inline. Format: `![Description](attachment-name.png)`
68 
69## Examples
70 
71**Input (voice dictation)**:
72> 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
73 
74**Output**:
75```markdown
76## Summary
77Agent deployment fails silently - no error displayed, agent disappears from list
78 
79## Environment
80- **Product/Service**: Azure AI Foundry
81- **Region/Version**: westus2
82 
83## Reproduction Steps
841. Navigate to agent deployment
852. Configure and deploy agent
863. Observe workflow completes
874. Check agent list
88 
89## Expected Behavior
90Agent appears in list with deployment status, errors shown if deployment fails
91 
92## Actual Behavior
93Agent disappears from list. No error message. Requires page refresh and retry.
94 
95## Impact
96**High** - Blocks agent deployment workflow, no feedback on failure cause
97 
98## Additional Context
99Required 3 retry attempts before successful deployment
100```
101 
102---
103 
104**Input (error paste)**:
105> Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.
106 
107**Output**:
108```markdown
109## Summary
110403 PERMISSION_DENIED error when publishing to Teams channel
111 
112## Environment
113- **Product/Service**: Copilot Studio → Teams integration
114- **Region/Version**: [REGION]
115 
116## Reproduction Steps
1171. Configure agent for Teams channel
1182. Attempt to publish
119 
120## Expected Behavior
121Agent publishes successfully to Teams channel
122 
123## Actual Behavior
124Returns `PERMISSION_DENIED` with code 403
125 
126## Error Details
127```
128Error: PERMISSION_DENIED
129Code: 403
130```
131 
132## Impact
133**High** - Blocks Teams integration, regression from previous working state
134 
135## Additional Context
136Was working yesterday - possible permission/config change or service regression
137```