| name | github-issue |
| description | Use to create, track, or manage GitHub issues with automatic project board integration (V2 and Classic), milestone tracking, and stage lifecycle (todo → in-progress → in-review → done). Covers issue creation, status updates, project board moves, and completion workflows.
|
GitHub Issue Management
Prerequisites
gh CLI installed and authenticated.- Working in a git repository with a GitHub remote.
Label Conventions
Type (required, one): bug, new-feature, improvement, refactor, security
Stage: todo, in-progress, in-review, done
Phase (optional): phase-1, etc.
Priority (optional): priority:high, priority:medium, priority:low
All labels use kebab-case. New issues start with todo.
Stage Lifecycle
todo → in-progress → in-review → done (closed)
Any stage can revert to todo if blocked.
Creating an Issue
- Gather context: what's the problem/feature, why, what "done" means, any examples.
- Detect repo setup: owner/repo, issue templates, Projects V2, Classic projects, milestones (see reference for exact command queries).
- Draft the issue using a standard template (Problem, Expected Outcome, Proposed Solution, Examples, Acceptance Criteria). If templates exist, adapt.
- Validate with user before creation.
- Create the issue via
gh issue create, add to project board (V2 or Classic using GraphQL), and associate milestone as appropriate.
- Confirm creation with issue number, labels, and links.
Updating an Issue
- Find the issue by number or search.
- Detect stage change (explicit or inferred).
- Update labels and stage, close when
done.
- Move on project board (V2/Classic) using GraphQL mutations.
- Confirm update.
For exact GraphQL queries and project board integration details, see PROJECTS_REFERENCE.md (loaded on demand).
