pr-comment-analyzer

# PR Comment Analysis Skill

When analyzing PR review comments, apply these principles:

## Comment Classification

### Actionable Comments (High Priority)
- Bug reports or potential issues
- Security concerns
- Performance problems
- Missing error handling
- Type safety issues
- Breaking changes

### Actionable Comments (Medium Priority)
- Code style violations
- Naming improvements
- Refactoring suggestions
- Documentation gaps
- Test coverage requests

### Non-Actionable Comments
- Praise or acknowledgments ("LGTM", "Nice!")
- Questions that need verbal response only
- Already resolved conversations
- Suggestions explicitly marked as optional/nitpick

## GitHub CLI Commands Reference

### Get PR for current branch
```bash
gh pr view --json number,title,url,state,baseRefName,headRefName
```

### Get review comments (inline comments on code)
```bash
gh api repos/{owner}/{repo}/pulls/{pr_number}/comments --jq '.[] | {id, path, line, body, user: .user.login, created_at, in_reply_to_id}'
```

### Get issue comments (general PR discussion)
```bash
gh api repos/{owner}/{repo}/issues/{pr_number}/comments --jq '.[] | {id, body, user: .user.login, created_at}'
```

### Get repo owner and name
```bash
gh repo view --json owner,name --jq '"\(.owner.login)/\(.name)"'
```

### Get review threads with resolution status
```bash
gh api graphql -f query='
  query($owner: String!, $repo: String!, $pr: Int!) {
    repository(owner: $owner, name: $repo) {
      pullRequest(number: $pr) {
        reviewThreads(first: 100) {
          nodes {
            isResolved
            comments(first: 10) {
              nodes {
                body
                author { login }
                path
                line
              }
            }
          }
        }
      }
    }
  }
' -f owner=OWNER -f repo=REPO -F pr=PR_NUMBER
```

## Response Strategy

When presenting comments to the user:

1. **Group by file** - Makes it easier to understand context
2. **Show severity** - Distinguis