github-ops

Automates GitHub workflows via gh CLI for PRs, issues, and searches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/chandima/opencode-config --skill github-ops-chandima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-ops
Source: https://github.com/chandima/opencode-config/tree/main/skills/github-ops
Command: npx skills add https://github.com/chandima/opencode-config --skill github-ops-chandima

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, base64, column, and includes scripts (resource) components.

What problem does it solve?

GitHub operations via gh CLI to manage PRs, issues, code search, and other GitHub tasks with MCP parity.

Core Features & Use Cases

  • Parity with MCP Server: manage PRs, issues, reviews, and searches using gh CLI across repos and organizations.
  • Automated governance: draft exact gh commands for reproducible workflows and auditing.
  • Real-world scenarios: handle PR reviews, issue triage, and code searches from a unified skill surface.

Quick Start

Run a sample operation, for example list PRs in a repository using the PRs script.

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 pull requests and issue triage across multiple repositories?

Automate GitHub pull requests and issue triage by running gh CLI commands from a scripts directory to manage workflows across repositories and organizations with deterministic JSON output. It handles PR management, issue triage, and code searches from a unified surface.

What is the best way to achieve MCP Server parity for GitHub operations without a direct integration?

Achieve MCP Server parity for GitHub operations by using gh CLI commands to manage PRs, issues, reviews, and searches. This approach drafts exact gh commands for reproducible workflows and auditing, replicating MCP Server capabilities natively.

Do I need jq and base64 installed to run gh CLI scripts for GitHub workflow automation?

Yes, you need jq, base64, column, and gh installed to run these GitHub workflow automation scripts. These dependencies handle JSON parsing, data decoding, and output formatting to ensure deterministic task execution and safe error handling.

Can I use gh CLI to search code across different organizations safely?

Yes, you can use gh CLI to search code across organizations safely. The scripts include safety checks and error handling while querying repositories, returning structured JSON output to ensure reproducible and auditable code search workflows.

How does frontmatter-driven discovery work for GitHub automation scripts?

Frontmatter-driven discovery works by using metadata headers to identify and route to the correct GitHub automation script in the scripts directory. This mechanism enables deterministic task execution, ensuring the right gh CLI command runs for the specific PR or issue operation.

What are the limitations of using gh CLI scripts for GitHub workflow automation?

Limitations of using gh CLI scripts include reliance on local CLI dependencies and constrained by API rate limits. While it provides JSON output and safety checks, complex multi-step GitHub workflow automation may require external orchestration beyond individual gh commands.