gh-pr-auto-detector

# GitHub PR Auto-Detector Skill

You have access to a skill that seamlessly integrates GitHub Pull Request context into conversations without polluting the main context window with huge PR payloads.

## Mission

Enhance user conversations by:
1. **Detecting** GitHub PR mentions in user messages
2. **Evaluating** whether PR context is genuinely needed
3. **Classifying** user intent to fetch reviews, CI, or full context
4. **Fetching** concise summaries via context-isolated subagent
5. **Integrating** information naturally into your response

## Pattern Recognition

### Detect these GitHub PR patterns:

**Full GitHub URLs:**
- Format: `https://github.com/[owner]/[repo]/pull/[number]`
- Examples:
  - `https://github.com/anthropics/claude-code/pull/123`
  - `https://github.com/owner/repo/pull/456`
- Common in: "Review https://github.com/owner/repo/pull/123"

**Short Form (owner/repo#number):**
- Format: `[owner]/[repo]#\d+`
- Examples: `anthropics/claude-code#123`, `owner/repo#456`
- Common in: "Check anthropics/claude-code#123"

**Hash-only (#number):**
- Format: `#\d+`
- Examples: `#123`, `#456`
- Common in: "What's the status of #123?"
- **CAVEAT**: Requires repository context from conversation or working directory

**Explicit Mentions:**
- "PR #123", "pull request 123", "PR 456"
- "the pull request #123"
- "review PR #456"

**Multiple PRs:**
- "Compare #123 and #456"
- "Review PRs #123, #124, #125"
- "Merged in anthropics/claude-code#123 and owner/repo#456"

## Intelligence: When to Fetch

### ✅ FETCH when user needs context:

**Direct questions:**
- "What is #123 about?"
- "Tell me about anthropics/claude-code#456"
- "What's in https://github.com/owner/repo/pull/789?"
- "Summarize PR #123"

**Review requests:**
- "Review #123"
- "Check the code in PR #456"
- "What do you think about anthropics/claude-code#123?"
- "Analyze this PR: [URL]"

**Status checks:**
- "What's the CI status of #123?"
- "Did the tests pass on #456?"
- "Are there any review comments on #123?"