github-ops

Manage GitHub issues, PRs, releases, and workflows via the gh CLI.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ARCASSystems/FounderOS --skill github-ops-arcassystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-ops
Source: https://github.com/ARCASSystems/FounderOS/tree/main/skills/github-ops
Command: npx skills add https://github.com/ARCASSystems/FounderOS --skill github-ops-arcassystems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill resolves the inefficiency and context switch involved in performing GitHub operations directly within a code-first interface like Claude Code.

Core Features & Use Cases

  • Centralized GitHub Actions: Perform a variety of GitHub actions like managing issues, pull requests, actions, and releases through the gh CLI.
  • Intuitive Integration: Direct integration with the gh CLI ensures operations remain within the coding environment, eliminating the need to switch tabs or contexts.
  • Command Execution: Execute operations like listing issues, commenting, closing issues, managing PRs, and checking release details without leaving Claude Code.

Quick Start

"Run 'list issues' to view open GitHub issues."

Frequently Asked Questions about github-ops

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

FAQPage Schema
How do I manage GitHub issues and pull requests without leaving my coding environment?

You can manage GitHub issues and pull requests directly through integrated `gh` CLI interactions. This allows you to list, comment, and close issues or PRs without switching contexts or leaving your code-first interface.

Can I check GitHub release details and workflow actions from within a code-first interface?

Yes, you can check release details and manage workflow actions from your interface. The tool executes `gh` CLI commands directly to retrieve release information and handle repository workflows seamlessly.

What is the best way to streamline GitHub repository management for development workflows?

Streamlining GitHub repository management is achieved by using direct `gh` CLI commands. It centralizes operations like issue tracking, PR reviews, and release management into a single coding interface.

Do I need the gh CLI installed to manage GitHub operations from my development environment?

Yes, the `gh` CLI is required. The skill relies entirely on direct `gh` CLI interactions to execute GitHub operations like managing issues, pull requests, and releases from within your interface.

Why should developers use direct command execution for GitHub operations instead of the web interface?

Direct command execution eliminates the inefficiency and context switching involved in using the web interface. It keeps GitHub operations like issue management and PR handling within the development environment.

Are there limitations to handling GitHub workflow actions through the gh CLI?

Operations are bound by `gh` CLI capabilities and permissions. While it handles issues, PRs, and releases efficiently, complex workflow actions may still require direct browser access depending on the GitHub configuration.