github-ops_skill

This skill orchestrates GitHub tasks using gh CLI and APIs, from PRs and issues to workflows and API queries, boosting automation and accuracy.

Python

609

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill daymade/claude-code-skills --skill github-ops

SKILL.md6.2 KB

Overview

This skill provides comprehensive GitHub operations using the gh CLI and GitHub REST/GraphQL APIs. It streamlines pull request and issue workflows, repository management, and GitHub Actions automation for both public GitHub and GitHub Enterprise. Use it to run, script, and automate common and advanced GitHub tasks reliably.

How this skill works

The skill issues gh CLI commands and formulates REST or GraphQL API calls to inspect and modify GitHub resources. It can create, view, edit, review, and merge pull requests; manage issues and repository settings; run and monitor workflows; and query API endpoints for structured JSON output. Authentication and configuration steps are handled with gh auth and gh config commands to support enterprise hosts and scripting environments.

When to use it

Creating, reviewing, or merging pull requests and enforcing title conventions
Creating, labeling, assigning, editing, or closing issues at scale
Cloning, creating, viewing, or configuring repositories and defaults
Running, monitoring, and debugging GitHub Actions workflows and runs
Querying REST or GraphQL endpoints for automation and reporting
Automating repeated operations across many repos or enterprise hosts

Best practices

Use gh auth login and set gh repo set-default to simplify scripts
Prefer JSON (--json) or template output for reliable parsing and jq processing
Adopt PR title conventions (JIRA prefix or NOJIRA) to integrate with tooling
Use GraphQL for complex queries that join related resources in one request
Handle pagination, rate limits, and retries in automation scripts

Example use cases

Create a NOJIRA or JIRA-linked pull request from CI and set reviewers
Bulk-close or relabel issues across multiple repositories using gh api
Run a workflow manually, stream its logs, and download artifacts for debugging
Query pull request metadata in JSON to feed a dashboard or release notes
Authenticate to a GitHub Enterprise host and set default repository for CI jobs

FAQ

Use gh auth login to set up authentication; gh manages tokens. For enterprise, include --hostname during login and ensure tokens have required scopes.

When should I use GraphQL vs REST?

Use REST for simple, single-resource calls. Use GraphQL when you need to fetch multiple related resources in one request to reduce round trips and simplify client-side joins.