# Issue Workflow

> Manage GitHub issues workflow - update status, add comments, create follow-ups. Use when starting work on an issue, completing an issue, or encountering blockers. Triggers on "issue", "close issue", "update issue", "blocked".

- Skill: `majiayu000/issue-workflow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/issue-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/issue-workflow/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/issue-workflow

---


# GitHub Issue Workflow Manager

## Instructions

### Starting Work on an Issue

1. Fetch issue details:
   ```bash
   gh issue view <number> --repo chaoming/ww2-flutter-game
   ```

2. Add "in progress" comment:
   ```bash
   gh issue comment <number> --repo chaoming/ww2-flutter-game --body "Started working on this issue."
   ```

### Completing an Issue

1. Ensure all acceptance criteria are met
2. Close the issue with a summary:
   ```bash
   gh issue close <number> --repo chaoming/ww2-flutter-game --comment "Completed. Summary of changes: ..."
   ```

### Creating Follow-up Issues

If work reveals additional tasks:
```bash
gh issue create --repo chaoming/ww2-flutter-game \
  --title "Follow-up: <title>" \
  --label "<label>" \
  --body "Discovered while working on #<parent-number>. ..."
```

### Handling Blockers

1. Add blocker comment:
   ```bash
   gh issue comment <number> --repo chaoming/ww2-flutter-game \
     --body "Blocked by: <reason>. Need: <what's needed>"
   ```

2. If blocked by another issue, link them:
   ```bash
   gh issue comment <number> --repo chaoming/ww2-flutter-game \
     --body "Blocked by #<blocking-issue>"
   ```

## Project Labels
- `foundation` - M1: Foundation phase
- `core-gameplay` - M2: Core gameplay phase
- `combat-ai` - M3: Combat & AI phase
- `polish` - M4: Polish & Modes phase
- `models` - Data models
- `ui` - User interface
- `game-logic` - Game logic & mechanics
- `ai` - AI opponent

