github-ops

Route GitHub operations through bash scripts for repositories, issues, and pull requests.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Thomashighbaugh/opencode --skill github-ops-thomashighbaugh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-ops
Source: https://github.com/Thomashighbaugh/opencode/tree/main/skills/github-ops
Command: npx skills add https://github.com/Thomashighbaugh/opencode --skill github-ops-thomashighbaugh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Provides a unified, script-driven interface to perform GitHub operations from the command line so users can avoid manual web workflows, craft exact gh commands, and automate repository, issue, PR, actions, and search tasks without extra token plumbing.

Core Features & Use Cases

  • Unified Router: Single entrypoint to route commands to domain scripts (repos, issues, prs, actions, releases, code-security, search, users, orgs, discussions, notifications, gists, projects).
  • Domain Scripts: Deterministic bash scripts implement full MCP parity for repositories, pull requests, issues, actions, releases, code security, discussions, notifications, gists, and projects v2.
  • Safety & Reliability: Confirmation prompts for destructive actions, consistent exit codes, JSON output options, limits, and error handling with retry semantics.
  • Operational Use Cases: List or view PRs and issues, fetch file contents, run and inspect Actions, create releases, manage orgs/teams, search code or repos, and generate exact gh CLI invocations for automation or human execution.

Quick Start

Use the router to list open pull requests for OWNER/REPO by running: bash scripts/router.sh prs list --owner OWNER --repo REPO --state open

Frequently Asked Questions about github-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issues and pull requests from the command line?

You can automate GitHub issues and pull requests by running bash scripts that invoke the gh CLI to list, view, create, and modify resources across OWNER/REPO contexts. The scripts provide deterministic execution with JSON output options and confirmation prompts for destructive actions.

What is the best way to manage GitHub Actions and releases without using the web interface?

Managing GitHub Actions and releases without the web interface is best done via a unified command-line router that dispatches gh CLI commands to domain scripts. This allows you to run and inspect Actions, create releases, and handle repository operations with consistent exit codes and retry semantics.

Do I need to install jq and git to manage GitHub repositories with gh CLI scripts?

Yes, you need to install and authenticate the gh CLI, install git for local operations, and install jq to support the bash scripts. These dependencies are required to parse JSON output, handle local repository management, and execute authenticated GitHub operations successfully.

How does the GitHub command-line router handle destructive actions like deleting repositories or modifying settings?

The GitHub command-line router handles destructive actions by implementing confirmation prompts before executing dangerous gh CLI commands. It also provides consistent exit codes, error handling with retry semantics, and JSON output toggles to ensure safe and reliable repository management.

Can I search code and manage GitHub discussions using bash scripts instead of the API directly?

Yes, you can search code and manage GitHub discussions using deterministic bash scripts that wrap the gh CLI, avoiding direct API token plumbing. The scripts support searching code or repos, managing discussions, and handling gists and projects v2.