Github Ops

What it does

This skill automates GitHub repository management tasks using the gh CLI tool and GitHub REST/GraphQL APIs. It enables AI agents to perform actions such as creating, viewing, editing, and merging pull requests; managing issues and repository settings; interacting with GitHub Actions workflows; querying API endpoints; and automating various GitHub operations. This includes integration with GitHub Enterprise instances.

When to use it

• 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

Key capabilities

• Pull Request Management: Creation, viewing, merging (including squash merges), reviewing, and commenting. Supports bypassing JIRA enforcement checks using the "NOJIRA" prefix in PR titles.
• Issue Management: Creation, listing, editing (adding labels), and closing issues.
• Repository Operations: Viewing repository details, cloning repositories, creating new public repositories.
• Workflow Management: Listing, running, watching, and downloading GitHub Actions workflows.
• API Interaction: Direct access to GitHub REST API endpoints via the gh api command; supports GraphQL queries for complex operations.
• Authentication & Configuration: Login (including GitHub Enterprise), status checks, setting default repositories, configuring gh settings, and managing output formats.
• Output Formatting: Control output format using JSON to facilitate programmatic processing.

Example prompts

• "Create a pull request titled 'NOJIRA: Fix typo in documentation' with the description 'Corrected a minor typographical error.'"
• "List all open issues labeled as 'bug'."
• "Run the workflow named 'deploy-to-production'."
• "Get details for pull request number 123 via API."

Tips & gotchas

• Authentication Required: The skill requires authentication with GitHub or GitHub Enterprise using gh auth login.
• API Familiarity: Using the gh api command effectively may require some understanding of GitHub's REST and GraphQL APIs.
• PR Title Conventions: PR titles should follow a specific convention: "GR-1234: Descriptive title" (with JIRA) or "NOJIRA: Descriptive title" (without JIRA).