OpenParable
Skip to content
← Back to skills

Issue Spec Github

Apps & Automation
issue-spec-github

Issue Spec Github is an Agent Skill for apps & automation published in the higress-group/higress repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use GitHub CLI for GitHub issues, pull requests, CI runs, and API queries that issue-spec does not wrap.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/higress-group/higress/blob/HEAD/.claude/skills/issue-spec-github/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-spec-github, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

GitHub CLI

Use the gh CLI to interact with GitHub repositories, issues, pull requests, CI, and API endpoints.

When To Use

  • Checking PR status, reviews, mergeability, or CI checks.
  • Creating, viewing, updating, closing, or commenting on GitHub issues.
  • Listing or inspecting pull requests, workflow runs, releases, labels, or repository metadata.
  • Calling GitHub API endpoints with gh api when issue-spec does not provide a dedicated command.

When Not To Use

  • Local git operations such as commit, branch, fetch, merge, or push. Use git directly.
  • Non-GitHub repositories. Use the matching provider CLI instead.
  • Complex code review across local diffs. Read the repository files directly and use issue-spec review commands for traceable findings.

Setup

gh auth login
gh auth status

Common Commands

gh issue list --repo owner/repo --state open
gh issue view 42 --repo owner/repo --json number,title,state,url,body
gh issue comment 42 --repo owner/repo --body "Comment body"

gh pr list --repo owner/repo
gh pr view 17 --repo owner/repo --json number,title,state,headRefName,baseRefName,url
gh pr checks 17 --repo owner/repo

gh run list --repo owner/repo --limit 10
gh run view <run-id> --repo owner/repo --log-failed

gh api repos/owner/repo/labels --jq '.[].name'

Notes

  • Always pass --repo owner/repo when the current directory is not definitely inside the target repository.
  • Use GitHub URLs directly when convenient, for example gh pr view https://github.com/owner/repo/pull/17.
  • Prefer structured output with --json and --jq when another command or agent step consumes the result.
  • issue-spec owns the proposal, design, implement, typed comment, review, verify, and archive workflow state. Use gh for adjacent GitHub operations that are outside issue-spec's command surface.