github-ops

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.

daymade/claude-code-skillsUpdated May 6, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

1

total installs

1

this week

784

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/daymade/claude-code-skills --skill github-ops

1

installs

1

this week

784

stars

Installation Guide

How to use github-ops on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add github-ops
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/daymade/claude-code-skills --skill github-ops

Fetches github-ops from daymade/claude-code-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/github-ops

Restart Cursor to activate github-ops. Access via /github-ops in your agent's command palette.

Security Notice

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.

Documentation

GitHub Operations

Overview

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.

When to Use This Skill

This skill activates for tasks involving:

  • Creating, viewing, editing, or merging pull requests
  • Managing GitHub issues or repository settings
  • Querying GitHub API endpoints (REST or GraphQL)
  • Working with GitHub Actions workflows
  • Performing bulk operations on repositories
  • Integrating with GitHub Enterprise
  • Automating GitHub operations via CLI or API

Core Operations

Pull Requests

# 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:

  • With JIRA ticket: GR-1234: Descriptive title
  • Without JIRA ticket: NOJIRA: Descriptive title

Issues

# 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

Repositories

# View and manage repos
gh repo view --web
gh repo clone owner/repo
gh repo create my-new-repo --public

Workflows

# 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

GitHub API

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.

Authentication and Configuration

# 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

Output Formats

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

Quick Reference

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

Resources

references/pr_operations.md

Comprehensive pull request operations including:

  • Detailed PR creation patterns (JIRA integration, body from file, targeting branches)
  • Viewing and filtering strategies
  • Review workflows and approval patterns
  • PR lifecycle management
  • Bulk operations and automation examples

Load this reference when working with complex PR workflows or bulk operations.

references/issue_operations.md

Detailed issue management examples including:

  • Issue creation with labels and assignees
  • Advanced filtering and search
  • Issue lifecycle and state management
  • Bulk operations on multiple issues
  • Integration with PRs and projects

Load this reference when managing issues at scale or setting up issue workflows.

references/workflow_operations.md

Advanced GitHub Actions workflow operations including:

  • Workflow triggers and manual runs
  • Run monitoring and debugging
  • Artifact management
  • Secrets and variables
  • Performance optimization strategies

Load this reference when working with CI/CD workflows or debugging failed runs.

references/best_practices.md

Shell scripting patterns and automation strategies including:

  • Output formatting (JSON, templates, jq)
  • Pagination and large result sets
  • Error handling and retry logic
  • Bulk operations and parallel execution
  • Enterprise GitHub patterns
  • Performance optimization

Load this reference when building automation scripts or handling enterprise deployments.

references/api_reference.md

Contains comprehensive GitHub REST API endpoint documentation including:

  • Complete API endpoint reference with examples
  • Request/response formats
  • Authentication patterns
  • Rate limiting guidance
  • Webhook configurations
  • Advanced GraphQL query patterns

Load this reference when performing complex API operations or when needing detailed endpoint specifications.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.565 reviews
  • L
    Liam AbbasDec 28, 2024

    Useful defaults in github-ops — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • L
    Liam RahmanDec 28, 2024

    Solid pick for teams standardizing on skills: github-ops is focused, and the summary matches what you get after install.

  • S
    Soo KhannaDec 24, 2024

    github-ops reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • K
    Kaira GarciaDec 20, 2024

    github-ops fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • K
    Kaira IyerDec 16, 2024

    We added github-ops from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • G
    Ganesh MohaneDec 12, 2024

    Registry listing for github-ops matched our evaluation — installs cleanly and behaves as described in the markdown.

  • E
    Evelyn ChoiDec 8, 2024

    github-ops is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • H
    Hana KhanNov 27, 2024

    github-ops fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • S
    Soo MenonNov 19, 2024

    I recommend github-ops for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • R
    Ren GillNov 19, 2024

    Registry listing for github-ops matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 65

1 / 7

Discussion

Comments — not star reviews
  • No comments yet — start the thread.