New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Issue Spec GitHub

by higress-group in higress-group/higress

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

MITAuto-check passedDevelopment

Install Issue Spec GitHub

skills CLI
$ npx skills add higress-group/higress --skill issue-spec-github -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install higress-group/higress issue-spec-github --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/higress-group/higress.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-spec-github .claude/skills/issue-spec-github && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
issue-spec-github
GitHub stars
9.5k
Token cost
~618 tokens
SKILL.md length
301 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

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

  • Tasks that involve Pull requests
  • SKILL.md covers Use and Setup and examples
  • Calls gh

What it does

Issue Spec GitHub is an agent skill from higress-group/higress. Use GitHub CLI for GitHub issues, pull requests, CI runs, and API queries that issue-spec does not wrap.

Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires GitHub CLI (gh).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: 🤖 AI Gateway | AI Native API Gateway. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/issue-spec-github”

Requirements

  • Compatibility (from SKILL.md): Requires GitHub CLI (gh).

What it can do on your machine

Read from SKILL.md and the folder at commit c74d7e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires GitHub CLI (gh).

    From compatibility in the SKILL.md frontmatter.

Context cost

Issue Spec GitHub loads about 618 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 301 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~618

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from higress-group/higress at commit c74d7e2, republished under its MIT licence (© higress-group). 301 words, ~618 tokens.

Download SKILL.mdSave it as .claude/skills/issue-spec-github/SKILL.md (or your agent's skills folder).
name
issue-spec-github
description
Use GitHub CLI for GitHub issues, pull requests, CI runs, and API queries that issue-spec does not wrap.
compatibility
Requires GitHub CLI (gh).
license
MIT
metadata.author
issue-spec
metadata.version
1.0
metadata.generatedBy
issue-spec

GitHub CLI

Use the gh CLI only for GitHub operations outside issue-spec's workflow and discussion surfaces.

Use

  • Inspect PR status, reviews, mergeability, CI, workflow runs, releases, labels, and repository metadata.
  • Use structured --json/--jq output. Use git directly for local repository operations.
  • After the code writer returns valuable line-rationale drafts, validate each stable path/symbol/changed-line anchor against the pushed exact head and confirm the rationale still applies and contains no secret, raw payload, or credential. Return invalid, stale, or sensitive drafts to the writer, or drop them with an explanation; never rewrite them while claiming worker authorship. Publish valid unchanged text as a GitHub-native inline PR comment by resolving commit_id, path, right-side line, and side=RIGHT after push. Writers need no GitHub access and never guess diff positions. Publish no filler.
  • Before human-review handoff, publish or refresh the ordinary GitHub PR discussion headed ### Implementation Rationale through gh pr comment <pr> --body-file <file> and use it as the summary/index for inline rationale. If a safe inline comment cannot be created, retain path:symbol/line plus the writer-authored rationale in this top-level discussion. Report requested write failure and retain the body without treating any rationale comment as evidence or delivery acceptance.
  • Ordinary issue discussion writes: write a body file and run issue-spec comment create --repo owner/repo --issue 42 --body-file reply.md --json. The selected issue backend owns the write. Never use GitHub CLI or a raw issue-comment API write.
  • issue-spec owns optional planning, implementation coordination, durable projection, PR context, and human handoff. The human and code host own current review, checks, approval, merge, and closing behavior. Do not use GitHub endpoints for non-GitHub providers.

Setup and examples

gh auth login
gh auth status
gh pr view 17 --repo owner/repo --json number,title,state,url
gh pr checks 17 --repo owner/repo
gh run view <run-id> --repo owner/repo --log-failed
gh api repos/owner/repo/labels --jq '.[].name'

© higress-group, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/issue-spec-github of higress-group/higress.

Open the folder on GitHubat commit c74d7e2

Compare with similar skills

Issue Spec GitHub next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Spec GitHub compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue Spec GitHub this skillhigress-group/higress9.5k—~618Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from higress-group/higress

All 11 skills in this repo

  • Higress Openclaw Integration

    higress-group/higress

    Deploy and configure Higress AI Gateway for OpenClaw integration.

    9.5k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed

  • Agent Session Monitor

    higress-group/higress

    Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage.

    9.5k GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Higress Wasm Go Plugin

    higress-group/higress

    Develop Higress WASM plugins using Go 1.24+. An agent skill from higress-group/higress.

    9.5k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Higress Auto Router

    higress-group/higress

    Configure automatic model routing using the get-ai-gateway.sh CLI tool for Higress AI Gateway.

    9.5k GitHub stars~954 tokensUpdated yesterday
    Auto-check passed

  • Higress Daily Report

    higress-group/higress

    生成 Higress 项目每日报告，追踪 issue/PR 动态，沉淀问题处理经验，驱动社区问题闭环。用于生成日报、跟进 issue、记录解决方案。

    9.5k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Issue Spec GitHub

What does Issue Spec GitHub do?

Use GitHub CLI for GitHub issues, pull requests, CI runs, and API queries that issue-spec does not wrap. Issue Spec GitHub is an agent skill from higress-group/higress. Use GitHub CLI for GitHub issues, pull requests, CI runs, and API queries that issue-spec does not wrap.

When should I use Issue Spec GitHub?

Issue Spec GitHub fits situations like: tasks that involve Pull requests.

How do I install Issue Spec GitHub in Claude Code?

Run `npx skills add higress-group/higress --skill issue-spec-github -a claude-code`. Or copy the skill folder (.agents/skills/issue-spec-github in higress-group/higress) into .claude/skills/issue-spec-github in your project. Claude Code loads it when a task matches its description.

How do I install Issue Spec GitHub in Codex?

Run `npx skills add higress-group/higress --skill issue-spec-github -a codex`. Or copy the skill folder (.agents/skills/issue-spec-github in higress-group/higress) into .agents/skills/issue-spec-github in your project. Codex loads it when a task matches its description.

Can I use Issue Spec GitHub in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add higress-group/higress --skill issue-spec-github -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-spec-github, .gemini/skills/issue-spec-github, .github/skills/issue-spec-github and .opencode/skills/issue-spec-github in your project.

What does Issue Spec GitHub need to run?

Going by SKILL.md and its folder, Issue Spec GitHub needs the command-line tools its instructions call (gh). Compatibility (from SKILL.md): Requires GitHub CLI (gh)..

Does Issue Spec GitHub access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Issue Spec GitHub safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Issue Spec GitHub use?

Issue Spec GitHub is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Issue Spec GitHub use?

About 618 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Issue Spec GitHub?

Skills that share tags, products or a category with Issue Spec GitHub: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Spec GitHub?

higress-group (a GitHub organization) maintains it in higress-group/higress, which has 9,505 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: higress-group/higress on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.