github-issue-analysis

# GitHub Issue Analysis Skill

Systematic methodology for analyzing GitHub issues to determine current relevance and appropriate action.

## Purpose

Analyze GitHub issues to determine:
- Is the issue still reproducible/relevant?
- Has it been fixed (find the PR/commit)?
- Does context need updating?
- Should it become a Linear ticket?

## Analysis Methodology

### Phase 1: Issue Data Collection

```bash
# Fetch complete issue details
gh issue view {issue_number} --json \
  title,body,labels,comments,createdAt,updatedAt,state,author
```

Extract from issue:
- **Title**: Main topic/symptom
- **Body**: Detailed description, steps to reproduce
- **Labels**: bug, enhancement, documentation, etc.
- **Comments**: Additional context, workarounds mentioned
- **Created Date**: Age of issue (older = more likely fixed)
- **Updated Date**: Last activity

### Phase 2: Keyword Extraction

From issue title and body, extract:

1. **Component Keywords**: UI elements, features mentioned
   - Example: "drawer", "sidebar", "modal", "canvas"

2. **Error Keywords**: Error messages, stack traces
   - Example: "undefined", "null", "404", "500"

3. **File/Function Keywords**: Specific code references
   - Example: "buildWidget", "AppDrawer.jsx"

4. **Behavior Keywords**: What's happening vs expected
   - Example: "redirects", "crashes", "freezes", "disappears"

### Phase 3: Codebase Search

Search for evidence the issue was addressed:

#### Search for Related Commits

```bash
# Search commit messages for issue keywords
git log --oneline --all --since="2025-01-01" --grep="{keyword}"

# Search for GitHub issue references in commits
git log --oneline --all --grep="#{issue_number}"

# Search for related file changes
git log --oneline --all --since="2025-01-01" -- "**/path/to/component*"
```

#### Search for Code Changes

```bash
# Check if the problematic code pattern still exists
rg "{error_pattern}" --type ts

# Check if fix patterns were added
rg "stopPropagation|preventDefault" --type tsx