github-issue-creator
/github-issue-creator
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.
- Author
- microsoft ↗
- Repository
- agent-skills ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Output Template
- Output Location
- Guidelines
- Examples
SKILL.md preview
--- name: github-issue-creator description: 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. --- # GitHub Issue Creator Transform messy input (error logs, voice notes, screenshots) into clean, actionable GitHub issues. ## Output Template ```markdown ## 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**: ```markdown ## 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**: ```markdown ## 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 ```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · microsoft/agent-skills | 95 | MIT |
| rootcastleco/rei-skills | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| google-gemini/gemini-cli | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 0a12ac54c591 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create-github-issue
Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue. - 100enter-issue
Create a GitHub issue from screenshots, images, text descriptions, or any combination. Use this when the user wants to file a new issue or report a bug. - 87github-screenshots
Embed screenshots, images, diagrams, GIFs, and screen recordings in GitHub PRs and issues — or stage them ahead of a PR, collect them into one attachments comment, or get a durable public link to share a visual with a person. Use this whenever a visual needs to end up in a PR… - 100fix-issue
Analyze and fix a GitHub issue for the iam-policy-validator project. Use when the user wants to fix a GitHub issue, resolve a bug report, or implement a feature request from an issue. Triggers on "/fix-issue", "fix issue #42", "resolve this GitHub issue", or "work on issue". - 100ac-issue
Reports issues to agentic-config repository via GitHub CLI. Supports bug reports and feature requests. Triggers on keywords: issue, report bug, feature request, ac issue - 90issue
Create a well-formed GitHub issue in the same format as the repo's issue forms, and optionally group it with labels, a project and a milestone, creating any that do not exist yet. Use when the user wants to raise, log or file an idea, request, feature, bug or task as a GitHub issue.