Github Issue Creator

by microsoft354361d83247No licenseListed Oct 8, 2026Updated Oct 8, 2026

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.

FeaturedInstructions onlyProductivity & Workflow
AI-generated overview

Turns raw notes, error logs, dictation, or screenshots into structured GitHub-flavored markdown issue reports.

What it does
This skill converts messy bug input such as error logs, voice dictation, informal descriptions, and screenshots into a clean, structured GitHub issue. It follows a fixed template covering summary, environment, reproduction steps, expected and actual behavior, error details, visual evidence, impact, and additional context. Output is written as markdown files in an /issues/ directory using a date-based filename convention. It also assigns severity levels and masks sensitive values with placeholders.
When to use it
Use it when a user pastes bug information, error messages, or informal descriptions and wants a structured GitHub issue. It fits situations where scattered notes or dictation need to be turned into an actionable report with reproduction steps and impact. It is also useful when screenshots or GIFs should be referenced as visual evidence.
Requirements
No scripts or special tooling are required; it is instructions only. It needs a writable /issues/ directory at the repository root for the generated markdown files.

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 Steps1. [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](attachment-name.png)

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
## SummaryAgent deployment fails silently - no error displayed, agent disappears from list
## Environment- **Product/Service**: Azure AI Foundry- **Region/Version**: westus2
## Reproduction Steps1. Navigate to agent deployment2. Configure and deploy agent3. Observe workflow completes4. Check agent list
## Expected BehaviorAgent appears in list with deployment status, errors shown if deployment fails
## Actual BehaviorAgent disappears from list. No error message. Requires page refresh and retry.
## Impact**High** - Blocks agent deployment workflow, no feedback on failure cause
## Additional ContextRequired 3 retry attempts before successful deployment

Input (error paste):

Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.

Output:

markdown
## Summary403 PERMISSION_DENIED error when publishing to Teams channel
## Environment- **Product/Service**: Copilot Studio → Teams integration- **Region/Version**: [REGION]
## Reproduction Steps1. Configure agent for Teams channel2. Attempt to publish
## Expected BehaviorAgent publishes successfully to Teams channel
## Actual BehaviorReturns `PERMISSION_DENIED` with code 403
## Error Details

Error: PERMISSION_DENIED Code: 403


## Impact**High** - Blocks Teams integration, regression from previous working state
## Additional ContextWas working yesterday - possible permission/config change or service regression

Source and attribution

Source:microsoft/skillsin.github/skills/github-issue-creatorat commit354361d

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal