affaan-m/github-ops
skills/github-ops/SKILL.md
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.
$ install --global
skillsauthnpx skillsauth add affaan-m/everything-claude-code github-opsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 3:18 AM22.6s1 file scanned
SKILL.md
- name:
- github-ops
- description:
- GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.
- origin:
- ECC
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
- Read the issue title, body, and comments
- Check if it duplicates an existing issue (search by keywords)
- Apply appropriate labels via
gh issue edit --add-label - For questions: draft and post a helpful response
- For bugs needing more info: ask for reproduction steps
- For good first issues: add
good-first-issuelabel - For duplicates: comment with link to original, add
duplicatelabel
# 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
- Check CI status:
gh pr checks <number> - Check if mergeable:
gh pr view <number> --json mergeable - Check age and last activity
- Flag PRs >5 days with no review
- For community PRs: ensure they have tests and follow conventions
Stale Policy
- Issues with no activity in 14+ days: add
stalelabel, 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-stalelabel)
# 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:
- Check the workflow run:
gh run view <run-id> --log-failed - Identify the failing step
- Check if it is a flaky test vs real failure
- For real failures: identify the root cause and suggest a fix
- For flaky tests: note the pattern for future investigation
# 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:
- Check all CI is green on main
- Review unreleased changes:
gh pr list --state merged --base main - Generate changelog from PR titles
- Create release:
gh release create
# 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
# Check Dependabot alerts
gh api repos/{owner}/{repo}/dependabot/alerts --jq '.[].security_advisory.summary'
# Check secret scanning alerts
gh api repos/{owner}/{repo}/secret-scanning/alerts --jq '.[].state'
# Review and auto-merge safe dependency bumps
gh pr list --label "dependencies" --json number,title
- Review and auto-merge safe dependency bumps
- Flag any critical/high severity alerts immediately
- Check for new Dependabot alerts weekly at minimum
Quality Gate
Before completing any GitHub operations task:
- all issues triaged have appropriate labels
- no PRs older than 7 days without a review or comment
- CI failures have been investigated (not just re-run)
- releases include accurate changelogs
- security alerts are acknowledged and tracked
Related Skills
affaan-m/dynamic-workflow-mode
data-ai
VerifiedTrustedCommunity
Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses.
207,422SKILL.mdUpdated Jun 5, 2026
affaan-m/react-testing
development
VerifiedTrustedCommunity
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
206,043SKILL.mdUpdated Jun 4, 2026
affaan-m/react-performance
tools
VerifiedTrustedCommunity
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
206,043SKILL.mdUpdated Jun 4, 2026
affaan-m/react-patterns
tools
VerifiedTrustedCommunity
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
197,464SKILL.mdUpdated May 29, 2026