Github Ops
Run GitHub repo hygiene—issue triage, PR and CI checks, releases, and security alerts—through the gh CLI.
Overview
github-ops is an agent skill most often used in Ship (also Operate, Grow) that manages GitHub issues, PRs, CI, releases, and security alerts via the gh CLI.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill github-opsWhat is this skill?
- Issue triage with type labels (bug, feature-request, good-first-issue) and four priority tiers
- PR management: review status, CI checks, merge readiness, stale PR handling
- CI/CD failure debugging and operational release/changelog prep
- Dependabot and security alert monitoring for open-source health
- End-to-end gh CLI workflows beyond basic git commit/push
- 7 issue type classes including duplicate and good-first-issue
- 4 priority tiers from critical to low
Adoption & trust: 3.1k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your GitHub repo is drowning in untriaged issues, red CI, and stale PRs and you do not have time to click through every screen.
Who is it for?
Solo founders and indie OSS maintainers who use GitHub as the system of record and want agent-assisted triage and ship checks.
Skip if: Teams on GitLab only, or developers who need local git rebasing tutorials without GitHub API operations.
When should I use this skill?
User wants GitHub issue triage, PR/CI management, releases, security alerts, or says check GitHub, triage issues, review PRs, merge, release, CI is broken.
What do I get? / Deliverables
Issues gain consistent labels and priority, PRs show merge readiness and CI status, and release or security follow-ups have a repeatable gh-driven workflow.
- Labeled and prioritized issues
- PR/CI status summaries
- Release and security action lists
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because most triggers are merge readiness, CI failures, and release prep before users see changes. PR review status, stale PRs, and CI gates are the primary workflow this skill automates.
Where it fits
Classify incoming bug reports and mark duplicates before a release branch freezes.
Draft release notes and verify CI green across the default branch.
Scan Dependabot and security alerts and open prioritized follow-up issues.
Label good-first-issue tickets and respond to documentation questions from new contributors.
How it compares
Operational gh playbook for repo health—not a replacement for code-review content skills that critique diffs line by line.
Common Questions / FAQ
Who is github-ops for?
Solo builders and small teams running GitHub-backed products or OSS who need structured issue, PR, CI, and release operations.
When should I use github-ops?
In Ship for PR/CI and releases; in Operate when monitoring Dependabot and alerts; in Grow when grooming good-first-issue and contributor backlog.
Is github-ops safe to install?
Check this page’s Security Audits panel; the skill drives gh API actions—scope gh auth minimally and review destructive merge/release commands.
SKILL.md
READMESKILL.md - 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 <number> --add-label "bug,high-priority" # Comment on issue gh issue comment <number> --body "Thanks for reporting. Could you share reproduction steps?" ``` ## 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) ```bash # Find stale issues (no activity in 14+ days) gh issue list --label "stale" --state open # Find PRs with no recent activity gh pr list --json number,title,updatedAt --jq '.[] | select(.updatedAt < "2026-03-01")' ``` ## 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. For real failures: identify the root cause and suggest a fix 5. For flaky tests: note the pattern for future investigation ```bash # List recent failed runs gh run list --status failure --limit 10 # View failed run logs gh run view <run-id> --log-failed # Re-run a failed workflow gh run rerun <run-id> --failed ``` ## Release Management When preparing a release: 1. Check all CI is green on main 2. Review unreleased changes: `gh pr list --state merged --base main` 3. Generate changelog from PR titles 4. Create release: `gh release create` ```bash # List merged PRs since last release gh pr list --state merged --base main --search "merged:>2026-03-01" # Create a release gh release create v1.2.0 --title "v1.2.0" --generate-notes # Create a pre-release gh release create v1.3.0-rc1 --prerelease --title "v1.3.0 Release Candidate 1" ``` ## Security Monitoring ```bash # Check Dependabot alerts gh api repos/{owner}/{repo}/dependabot/alerts --jq '.[].security_advisory.summary' # Check secret scanning alerts gh