dhpk-issue-analyzelisted

# Issue Analyze Skill ## Input Types | Type | Source | Example | |------|--------|---------| | GitHub Issue | Issue number, URL, or description | `/dhpk:dhpk-issue-analyze 123` | | Review Thread | file:line + reviewer comment | `/dhpk:dhpk-issue-analyze --triage "src/foo.ts:42 — Use early return"` | When input is a **Review Thread**: - Phase 1 skips `gh issue view`, uses provided thread data directly - Phase 2 classification uses Review Thread dimensions (see `references/classification.md`) ## Modes | Mode | Input Type | Phases Executed | Use Case | |------|-----------|----------------|----------| | Full (default) | Issue or Thread | 1 → 2 → 2.5 → 3 → 4 | Deep analysis with investigation | | Triage (`--triage`) | Review Thread | 2 → 2.5 only | Lightweight classification + verdict (thread data provided inline) | | Triage (`--triage`) | GitHub Issue | 1 → 2 → 2.5 | Fetch issue first, then classify + verdict | ## When NOT to Use - Known root cause, fix directly (use `/dhpk:dhpk-adaptive-dev-workflow` and select the Bug branch) - Pure feature development (use `/dhpk:dhpk-adaptive-dev-workflow` and select the Feature branch) - Only need code review (use `/codex-review`) ## Workflow 1. **Read** the issue with `gh issue view --json ...`, or use the supplied review-thread fields. Extract symptoms, reproduction, errors, and file clues. 2. **Classify** with [classification.md](references/classification.md): unfamiliar → `/dhpk:dhpk-codebase-exploration`; regression → `/dhpk:dh