Github Issue Creator
Scanned@thegovind
npx machina-cli add skill @thegovind/github-issue-creator --openclawGitHub Issue Creator
Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues.
Output Template
## Summary
[One-line description of the issue]
## Environment
- **Product/Service**:
- **Region/Version**:
- **Browser/OS**: (if relevant)
## Reproduction Steps
1. [Step]
2. [Step]
3. [Step]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Error Details
[Error message/code if applicable]
## Visual Evidence
[Reference to attached screenshots/GIFs]
## Impact
[Severity: Critical/High/Medium/Low + brief explanation]
## Additional Context
[Any other relevant details]
Output Location
Create issues as markdown files in /issues/ directory at the repo root. Use naming convention: 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: 
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:
## 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
Input (error paste):
Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.
Output:
## Summary
403 PERMISSION_DENIED error when publishing to Teams channel
## Environment
- **Product/Service**: Copilot Studio → Teams integration
- **Region/Version**: [REGION]
## Reproduction Steps
1. Configure agent for Teams channel
2. Attempt to publish
## Expected Behavior
Agent publishes successfully to Teams channel
## Actual Behavior
Returns `PERMISSION_DENIED` with code 403
## Error Details
Error: PERMISSION_DENIED Code: 403
## Impact
**High** - Blocks Teams integration, regression from previous working state
## Additional Context
Was working yesterday - possible permission/config change or service regression
Overview
GitHub Issue Creator transforms raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored Markdown issues. It outputs complete Markdown files that map to the repository’s /issues/ directory using the standard YYYY-MM-DD-short-description.md naming convention. It also supports attaching images/GIFs and uses placeholders for sensitive data like [PROJECT_NAME].
How This Skill Works
Feed the tool with bug notes or visuals. It extracts structured fields (Summary, Environment, Reproduction Steps, Expected Behavior, Actual Behavior, Error Details, Visual Evidence, Impact, Additional Context) and formats them into the GitHub issue Output Template. The result is a ready-to-commit Markdown file saved under /issues/YYYY-MM-DD-short-description.md.
When to Use It
- User-reported bugs with scattered notes and no proper GitHub issue
- Error logs or stack traces that need organizing into a structured report
- Voice-dictated bug reports that lack precise formatting
- Screenshots or GIFs used as visual evidence for bugs
- New issues for regressions or incidents requiring formal tracking
Quick Start
- Step 1: Paste raw notes, error logs, or upload screenshots into the GitHub Issue Creator
- Step 2: Review auto-extracted sections and attach visuals; replace placeholders as needed
- Step 3: Save to /issues/YYYY-MM-DD-short-description.md and commit to the repo
Best Practices
- Be crisp: extract concrete steps, expected/actual outcomes, and impact
- Ensure all sections from Summary to Additional Context are present
- Reference attachments inline with Markdown image syntax
- Use placeholders like [PROJECT_NAME], [USER_ID] to protect sensitive data
- Verify environment details (Product/Service, Region/Version, OS) before saving
Example Use Cases
- Bug: Login fails with 401 after password reset, no error message shown
- Error: Unhandled exception on CSV export (ArrayIndexOutOfBounds) in v2.3.1
- UI: Dashboard widgets misaligned on EU region after latest deploy
- Performance: Reports page times out after 60s in sandbox environment
- Privilege: PERMISSION_DENIED (403) when publishing to Teams channel in Copilot Studio integration