issue-spec-github

Inspect GitHub pull requests, CI runs, and repository metadata using the GitHub CLI.

9.3k|1.3k|Updated Oct 27, 2022
One-click install
npx skills add https://github.com/alibaba/higress --skill issue-spec-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-spec-github
Source: https://github.com/alibaba/higress/tree/main/.agents/skills/issue-spec-github
Command: npx skills add https://github.com/alibaba/higress --skill issue-spec-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with issue-spec workflows, you still need direct access to GitHub operations that issue-spec does not wrap, such as checking PR status, reviewing CI runs, and querying repository metadata. This Skill defines when and how to use the GitHub CLI (gh) for those operations without conflicting with issue-spec's owned surfaces.

Core Features & Use Cases

  • PR and CI Inspection: View pull request status, reviews, mergeability, checks, workflow runs, releases, and labels using structured --json/--jq output.
  • Inline Rationale Publishing: Validate writer-authored line-rationale drafts against the pushed head commit and publish them as GitHub-native inline PR comments with resolved commit_id, path, and line anchors.
  • Review Handoff Summaries: Publish or refresh a top-level 'Implementation Rationale' PR discussion via gh pr comment before human review handoff.
  • Use Case: After a code writer returns rationale drafts, validate each anchor against the pushed commit, publish valid ones as inline comments, and post the summary discussion so reviewers see the full context.

Quick Start

Ask the assistant to check the status and CI results of pull request 17 in your repository using the GitHub CLI.

Frequently Asked Questions about issue-spec-github

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

FAQPage Schema
How do I check pull request status with the GitHub CLI?

Run gh pr view <number> --repo owner/repo --json number,title,state,url to get structured PR details, and gh pr checks <number> to see CI check results. The --json and --jq flags give machine-readable output for scripting.

How to view failed CI workflow runs using gh?

Use gh run view <run-id> --repo owner/repo --log-failed to inspect only the failed job logs of a workflow run. This filters output to the failing steps instead of dumping entire logs.

When should I use gh CLI instead of issue-spec commands?

Use gh only for operations issue-spec does not wrap, such as PR status, CI runs, releases, labels, and repository metadata. Ordinary issue discussion writes must go through issue-spec comment create, never through gh or raw issue-comment API calls.

Does this Skill work with GitLab or other code hosts?

No. The GitHub CLI only supports GitHub repositories, and the Skill explicitly says not to use GitHub endpoints for non-GitHub providers. Other platforms require their own CLI or API tooling.

What are the prerequisites for using the GitHub CLI?

Install the gh CLI and authenticate with gh auth login, then verify access with gh auth status. Local git operations like commits and pushes still use git directly, not gh.