Agent skill · software engineering · affaan-m
github-ops
GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー。
Why this skill is useful
Adds specific commands and workflows for managing GitHub operations that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
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 PR Management Review Checklist 1. Check CI status: gh pr checks <number> 2. Check if mergeable: gh pr view <number> --json mergeable 3. Check age and last activity 4. Flag PRs >5 days with no review 5. For community PRs: ensure they have tests and follow conventions Stale Policy Issues with no activity in 14+ days: add stale label, comment asking for update PRs with no activity in 7+ days: comment asking if still active Auto-close stale issues after 30 days with no response (add closed-stale label) CI/CD Operations When CI fails: 1. Check the workflow run: gh run view <run-id> --log-failed 2. Identify the failing step 3. Check if it is a flaky test vs real failure 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/github-ops--738a6b