github-ops

# GitHub Operations Manage GitHub repositories with a focus on community health, CI reliability, and contributor experience. ## When to Activate - Triaging issues (classifying, labeling, responding, deduplicating) - Managing PRs (review status, CI checks, stale PRs, merge readiness) - Debugging CI/CD failures - Preparing releases and changelogs - Monitoring Dependabot and security alerts - Managing contributor experience on open-source projects - User says "check GitHub", "triage issues", "review PRs", "merge", "release", "CI is broken" ## Tool Requirements - **gh CLI** for all GitHub API operations - Repository access configured via `gh auth login` ## Issue Triage Classify each issue by type and priority: **Types:** bug, feature-request, question, documentation, enhancement, duplicate, invalid, good-first-issue **Priority:** critical (breaking/security), high (significant impact), medium (nice to have), low (cosmetic) ### Triage Workflow 1. Read the issue title, body, and comments 2. Check if it duplicates an existing issue (search by keywords) 3. Apply appropriate labels via `gh issue edit --add-label` 4. For questions: draft and post a helpful response 5. For bugs needing more info: ask for reproduction steps 6. For good first issues: add `good-first-issue` label 7. For duplicates: comment with link to original, add `duplicate` label ```bash # Search for potential duplicates gh issue list --search "keyword" --state all --limit 20 # Add labels gh issue edit <nu...