This skill provides comprehensive guidance for GitHub operations using the gh CLI tool and GitHub REST/GraphQL APIs. Use this skill when performing any GitHub-related tasks including pull request management, issue tracking, repository operations, workflow automation, and API interactions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongithub-opsExecute the skills CLI command in your project's root directory to begin installation:
Fetches github-ops from daymade/claude-code-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate github-ops. Access via /github-ops in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
784
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
784
stars
This skill provides comprehensive guidance for GitHub operations using the gh CLI tool and GitHub REST/GraphQL APIs. Use this skill when performing any GitHub-related tasks including pull request management, issue tracking, repository operations, workflow automation, and API interactions.
This skill activates for tasks involving:
# Create PR with NOJIRA prefix (bypasses JIRA enforcement checks)
gh pr create --title "NOJIRA: Your PR title" --body "PR description"
# List and view PRs
gh pr list --state open
gh pr view 123
# Manage PRs
gh pr merge 123 --squash
gh pr review 123 --approve
gh pr comment 123 --body "LGTM"
📚 See references/pr_operations.md for comprehensive PR workflows
PR Title Convention:
GR-1234: Descriptive titleNOJIRA: Descriptive title# Create and manage issues
gh issue create --title "Bug: Issue title" --body "Issue description"
gh issue list --state open --label bug
gh issue edit 456 --add-label "priority-high"
gh issue close 456
📚 See references/issue_operations.md for detailed issue management
# View and manage repos
gh repo view --web
gh repo clone owner/repo
gh repo create my-new-repo --public
# Manage GitHub Actions
gh workflow list
gh workflow run workflow-name
gh run watch run-id
gh run download run-id
📚 See references/workflow_operations.md for advanced workflow operations
The gh api command provides direct access to GitHub REST API endpoints. Refer to references/api_reference.md for comprehensive API endpoint documentation.
Basic API operations:
# Get PR details via API
gh api repos/{owner}/{repo}/pulls/{pr_number}
# Add PR comment
gh api repos/{owner}/{repo}/issues/{pr_number}/comments \
-f body="Comment text"
# List workflow runs
gh api repos/{owner}/{repo}/actions/runs
For complex queries requiring multiple related resources, use GraphQL. See references/api_reference.md for GraphQL examples.
# Login to GitHub
gh auth login
# Login to GitHub Enterprise
gh auth login --hostname github.enterprise.com
# Check authentication status
gh auth status
# Set default repository
gh repo set-default owner/repo
# Configure gh settings
gh config set editor vim
gh config set git_protocol ssh
gh config list
Control output format for programmatic processing:
# JSON output
gh pr list --json number,title,state,author
# JSON with jq processing
gh pr list --json number,title | jq '.[] | select(.title | contains("bug"))'
# Template output
gh pr list --template '{{range .}}{{.number}}: {{.title}}{{"\n"}}{{end}}'
📚 See references/best_practices.md for shell patterns and automation strategies
Most Common Operations:
gh pr create --title "NOJIRA: Title" --body "Description" # Create PR
gh pr list # List PRs
gh pr view 123 # View PR details
gh pr checks 123 # Check PR status
gh pr merge 123 --squash # Merge PR
gh pr comment 123 --body "LGTM" # Comment on PR
gh issue create --title "Title" --body "Description" # Create issue
gh workflow run workflow-name # Run workflow
gh repo view --web # Open repo in browser
gh api repos/{owner}/{repo}/pulls/{pr_number} # Direct API call
Comprehensive pull request operations including:
Load this reference when working with complex PR workflows or bulk operations.
Detailed issue management examples including:
Load this reference when managing issues at scale or setting up issue workflows.
Advanced GitHub Actions workflow operations including:
Load this reference when working with CI/CD workflows or debugging failed runs.
Shell scripting patterns and automation strategies including:
Load this reference when building automation scripts or handling enterprise deployments.
Contains comprehensive GitHub REST API endpoint documentation including:
Load this reference when performing complex API operations or when needing detailed endpoint specifications.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in github-ops — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: github-ops is focused, and the summary matches what you get after install.
github-ops reduced setup friction for our internal harness; good balance of opinion and flexibility.
github-ops fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added github-ops from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for github-ops matched our evaluation — installs cleanly and behaves as described in the markdown.
github-ops is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
github-ops fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend github-ops for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for github-ops matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 65