github-ops

name

github-ops

description

Shared how-to for GitHub operations in both environments this system runs in — locally with the `gh` CLI + `git`, and on Claude web / in scheduled routines with the GitHub MCP server (`mcp__github__*`, no `gh` there). One operation catalog, two reference files for the GitHub mechanism, plus a CI-provider reference so the "read CI status / read a failing log" operations resolve to GitHub checks or Azure Pipelines — which of the two is chosen inside the `ops-ci` capability, not here and not in any config key. The loop skills point here instead of each re-explaining the dual path. Load this whenever a loop needs to touch GitHub (list/create issues, open/merge PRs, check CI, push files) and you need the concrete command/tool for the current environment.

github-ops

The loops in this marketplace run in two environments, and GitHub is reached differently in each. This skill is the single source of truth for that mapping so no loop skill has to repeat it.

Pick the mechanism by environment

flowchart LR
    START{"is gh available?<br/>(run: command -v gh)"} -->|yes — dev machine| CLI["gh CLI + git<br/>→ references/gh-cli.md"]
    START -->|no — Claude web / routine| MCP["GitHub MCP server<br/>(mcp__github__*)<br/>→ references/github-mcp.md"]

• Local (dev machine): gh and git are installed → use references/gh-cli.md. Auth is your gh login.
• Claude web / scheduled routine: gh is not available; the GitHub MCP server is → use references/github-mcp.md. Auth is the MCP server's connected GitHub App (no token to paste).

Both are first-class. Detect with command -v gh (or: if the mcp__github__* tools are present, you're on the MCP path). under are a third, separate case — they call the REST API with directly and are out of scope here.