# Github Issue Creator

> Structure bug reports, requirements, logs, or screenshots into actionable GitHub issues. Use it when you need acceptance criteria, scope definition, and a validation plan.

- Skill: `lteawoo/github-issue-creator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add lteawoo/github-issue-creator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lteawoo/github-issue-creator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lteawoo (https://skillmd.com/u/lteawoo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lteawoo/github-issue-creator

---


# GitHub Issue Creator

## Purpose
Turn unstructured input into a GitHub issue that is ready for development.

## Core Principles
1. Put the acceptance criteria at the top using Given/When/Then.
2. Separate In Scope from Out of Scope.
3. An issue without a validation plan, automated or manual, is not complete.
4. If information is missing, ask follow-up questions instead of guessing.
5. Replace sensitive information with placeholders such as `[USER_ID]` or `[TOKEN]`.
6. Include at least one recommended PR label for release categorization in the issue body.

## Release Label Hints
Based on `.github/release.yml`, PR labels determine the release category.

- `New Features`: `feat`, `feature`, `enhancement`
- `Bug Fixes`: `fix`, `bug`, `bugfix`
- `Maintenance (Chore)`: `chore`, `dependencies`, `ci`, `build`, `refactor`
- Unmatched or missing labels: `Other Changes`

Recommended:
1. Include the `recommended PR label` in the issue.
2. Apply the same label on the implementation PR to avoid release-note classification gaps.

## Output Format

### Title
- `[type] one-line summary`
- type: `feat|fix|refactor|docs|chore|test`

### Acceptance Criteria
- Given ...
- When ...
- Then ...

### Background or Problem
- Current state
- User or operational impact

### Scope
- In Scope
- Out of Scope

### Implementation Direction
- Target areas or modules
- Constraints and dependencies
- Risks
- Recommended PR label (`feat|feature|enhancement|fix|bug|bugfix|chore|dependencies|ci|build|refactor`)

### Validation Plan
- Automated validation: lint, build, test
- Manual validation: key scenarios
- For UI changes: screenshot checkpoints

### Completion Criteria
- AC satisfied
- No regressions
- Release impact and cautions documented

### Checklist
- [ ] Implementation complete
- [ ] Tests complete
- [ ] Regression check complete
- [ ] Recommended PR label assigned or confirmed
- [ ] Docs or release notes updated if needed

## When Information Is Missing
- Draft the issue first.
- Limit follow-up questions to three.