github-workflows

Automates GitHub pull requests, issues, CI checks, and releases using the gh CLI.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill github-workflows-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflows
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/github-workflows
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill github-workflows-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It eliminates error-prone manual GitHub operations by enforcing a single rule: every GitHub task — PRs, issues, CI status, labels, reviews, merges, releases — goes through the gh CLI instead of the browser or raw API calls. ## Core Features & Use Cases - Full PR lifecycle: create PRs with spec-traceable bodies, edit titles/labels/reviewers, post inline review comments pinned to diff lines via gh api, and merge with squash, rebase, or auto-merge. - CI monitoring and control: check PR status, watch workflow runs live, view logs, and rerun failed jobs before merging. - Issues, labels, milestones, and releases: manage the full project surface, including JSON output with --jq for scripting. - Use Case: After pushing a feature branch, create a PR with a spec reference, watch CI until green, then squash-merge and delete the branch — all without leaving the terminal. ## Quick Start Ask the agent to create a pull request for the current branch with a proper title and spec reference, then watch CI and squash-merge when checks pass.

Frequently Asked Questions about github-workflows

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

FAQPage Schema
How do I create a GitHub pull request from the command line?

Use gh pr create with --title, --body, --base, and --head flags after pushing your branch. The body should include a summary, spec reference, and test plan checklist; add --draft to open it as a draft.

How do I post inline review comments on specific diff lines with gh?

gh pr review only posts a body, so use gh api to POST to repos/{owner}/{repo}/pulls/{number}/reviews with a comments array containing path, line, side, and body. Set side to RIGHT for new-file lines and include the head commit SHA as commit_id.

How do I wait for GitHub CI checks to pass before merging?

Use gh run watch with the run ID to stream until completion, or gh pr checks to view status. For automatic merging once CI passes, use gh pr merge --auto --squash.

When should I use gh api instead of gh subcommands?

Use gh api only when gh has no native subcommand for the operation, such as posting reviews with inline comments or GraphQL queries. The :owner and :repo placeholders auto-resolve from the current git remote.

Why should I avoid curl against the GitHub API?

gh handles authentication, pagination, and structured JSON output automatically, while raw curl requires manual token management and error handling. The skill mandates gh for every operation the CLI supports.