GitHub Issue Creator
Produce a GitHub issue draft from conversation context or rough input.
Output
Write the draft to .github/drafts/issue-draft.md — always this exact path — creating the directory if needed and overwriting any existing file.
File format — follow this exactly
The file has YAML frontmatter for the title and labels, followed by the issue body.
---
title: "feat: add bulk export for user activity logs"
labels: [feature]
---
Allow admins to export user activity logs as CSV for compliance auditing. No current way to extract this data without direct DB access.
- [ ] Add date range picker to activity logs page
- [ ] Implement backend endpoint for filtered CSV generation
- [ ] Handle large exports via streaming or background job
- [ ] Add export button to admin UI with loading state
- [ ] Include columns: user, action, timestamp, IP, resource
- [ ] Write tests for export endpoint edge cases
- [ ] Update admin docs with export instructions
Rules
- Title: use
feat:, fix:, refactor:, docs:, chore: prefix when obvious. Keep under 70 chars.
- Labels: draw only from the preset
.claude/skills/label-setup/labels.yml — never a label outside it. Keep the set small: usually one type label (e.g. feature, bug), optionally paired with one priority: label. Use an empty list when none apply.
- Each checkbox = a coherent unit of work. Not micro-steps, not mega-tasks.
- Keep checkboxes between 4–20. If exceeding 20, consolidate first. If still over 20, split into separate issues — produce the first one, suggest follow-up titles with one-line descriptions, and ask the user if they want those written out.
- Add
### Context or ### Notes only when there's genuinely useful background. Otherwise omit entirely.
- Never post to GitHub; never run
gh, git, or any network call.
After writing
Do not render the draft in chat — the user reviews the file in their editor. Show the file path and ask them to choose:
- Happy, publish — hand off to the
issue-publish skill.
- Needs change — revise the draft, rewrite the file, and ask again.
- Happy, but don't publish now — stop; the draft file stays for later.
- Something else — open-ended.
1---2name: github-issue-creator3description: "Use this skill whenever the user wants to create a GitHub issue, write up a task or bug report for GitHub, or turn a conversation or rough explanation into a structured GitHub issue — including a described feature, bug, or task the user asks to formalize. Drafts only: writes a local draft file, never posts to GitHub, never runs `gh`."4metadata:5 source: https://skillmd.com/skills/nagarenegishi/github-issue-creator6---78# GitHub Issue Creator910Produce a GitHub issue draft from conversation context or rough input.1112## Output1314Write the draft to `.github/drafts/issue-draft.md` — always this exact path — creating the directory if needed and overwriting any existing file.1516## File format — follow this exactly1718The file has YAML frontmatter for the title and labels, followed by the issue body.1920```markdown21---22title: "feat: add bulk export for user activity logs"23labels: [feature]24---25 26Allow admins to export user activity logs as CSV for compliance auditing. No current way to extract this data without direct DB access.27 28- [ ] Add date range picker to activity logs page29- [ ] Implement backend endpoint for filtered CSV generation30- [ ] Handle large exports via streaming or background job31- [ ] Add export button to admin UI with loading state32- [ ] Include columns: user, action, timestamp, IP, resource33- [ ] Write tests for export endpoint edge cases34- [ ] Update admin docs with export instructions35```3637## Rules3839- Title: use `feat:`, `fix:`, `refactor:`, `docs:`, `chore:` prefix when obvious. Keep under 70 chars.40- Labels: draw only from the preset `.claude/skills/label-setup/labels.yml` — never a label outside it. Keep the set small: usually one type label (e.g. `feature`, `bug`), optionally paired with one `priority:` label. Use an empty list when none apply.41- Each checkbox = a coherent unit of work. Not micro-steps, not mega-tasks.42- Keep checkboxes between 4–20. If exceeding 20, consolidate first. If still over 20, split into separate issues — produce the first one, suggest follow-up titles with one-line descriptions, and ask the user if they want those written out.43- Add `### Context` or `### Notes` only when there's genuinely useful background. Otherwise omit entirely.44- Never post to GitHub; never run `gh`, `git`, or any network call.4546## After writing4748Do not render the draft in chat — the user reviews the file in their editor. Show the file path and ask them to choose:49501. **Happy, publish** — hand off to the `issue-publish` skill.512. **Needs change** — revise the draft, rewrite the file, and ask again.523. **Happy, but don't publish now** — stop; the draft file stays for later.534. **Something else** — open-ended.