Convert raw notes, error logs, voice dictation, or screenshots into structured GitHub-flavored markdown issue reports. Use when creating issues from unstructured input, converting meeting notes to action items, or structuring bug reports from user feedback. Adapted from microsoft/skills for the Anokye System.
Convert unstructured input into well-structured GitHub issues using org-standard issue types (Epic, Feature, Task, Bug) and GraphQL mutations.
## Summary
[1-2 sentence description of what and why]
## Details
[Expanded context, requirements, or reproduction steps]
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Notes
[Additional context, links, references]
| Type | When to Use |
|---|---|
| Epic | Large initiative spanning multiple features |
| Feature | User-facing capability or enhancement |
| Task | Implementation work, chore, or technical item |
| Bug | Defect, regression, or unexpected behavior |
Always use GraphQL mutations (never REST) for issue creation:
mutation {
createIssue(input: {
repositoryId: "<REPO_ID>"
title: "<title>"
body: "<body>"
issueTypeId: "<ISSUE_TYPE_ID>"
}) {
issue { number url }
}
}
When given unstructured input:
Add retry logic to webhook delivery not Webhook issue#number referencesAdapted from microsoft/skills github-issue-creator skill (MIT License).