issue-status-sync

# GitHub Issue Status Sync Skill

This skill provides patterns for keeping GitHub issues synchronized with actual development progress.

## GitHub Issue Status Model

Unlike Jira, GitHub issues have simple states:
- **Open**: Active, needs work
- **Closed**: Complete or won't fix

Status is conveyed through:
- Labels (in progress, blocked, etc.)
- Milestones
- Project board columns
- Comments

---

## Status Labels

### Recommended Label Set

**Workflow:**
- `needs-triage` - Needs initial review
- `needs-info` - Waiting for reporter
- `in progress` - Being worked on
- `blocked` - Cannot proceed
- `ready for review` - PR ready
- `ready for merge` - Approved, waiting merge

**Type:**
- `bug`
- `enhancement`
- `documentation`
- `chore`

**Priority:**
- `priority: critical`
- `priority: high`
- `priority: medium`
- `priority: low`

### Status Transitions via Labels

```bash
# Starting work
gh issue edit {number} --add-label "in progress" --remove-label "needs-triage"

# Blocked
gh issue edit {number} --add-label "blocked"

# Ready for review
gh issue edit {number} --add-label "ready for review" --remove-label "in progress"

# Complete
gh issue close {number} --comment "Completed in PR #456"
```

---

## Progress Updates

### Starting Work

```bash
gh issue edit {number} --add-assignee @me --add-label "in progress"
gh issue comment {number} --body "$(cat <<'EOF'
Starting work on this issue.

**Approach:**
- [Brief description]

**Branch:** `feature/{number}-description`

**ETA:** [Rough estimate]
EOF
)"
```

### Progress Update

```bash
gh issue comment {number} --body "$(cat <<'EOF'
**Progress Update**

**Completed:**
- [What's done]

**In Progress:**
- [Current work]

**Next:**
- [What's planned]

**Blockers:** None / [Description]
EOF
)"
```

### Blocked

```bash
gh issue edit {number} --add-label "blocked"
gh issue comment {number} --body "$(cat <<'EOF'
**Blocked**

**Reason:** [Clear explanation]
**Blocked by:** #123 / [External factor]
**Action needed:** [What woul