Github Issue Creator
Github Issue Creator is an code AI skill with a core value of Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. It
helps developers solve real-world problems in the code domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
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 wan...
Quick Facts
mkdir -p ./skills/github-issue-creator && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/github-issue-creator/SKILL.md -o ./skills/github-issue-creator/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# GitHub 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: `!Description`
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 DetailsError: 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 regressionWhen to Use
This skill is applicable to execute the workflow or actions described in the overview.
🎯 Best For
- Claude users
- Software engineers
- Development teams
- Tech leads
💡 Use Cases
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Github Issue Creator to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is Github Issue Creator compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for Github Issue Creator?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install Github Issue Creator?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/github-issue-creator/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.