Agent skill

Gh Issues

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

MITAuto-check passedDevelopment

Install Gh Issues

skills CLI

$ npx skills add openclaw/openclaw --skill gh-issues -a claude-code

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

GitHub CLI

$ gh skill install openclaw/openclaw gh-issues --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/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gh-issues .claude/skills/gh-issues && 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/

Paste into Claude Code

Install the "gh-issues" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/gh-issues into .claude/skills/gh-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-issues", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/openclaw/openclaw/tree/main/skills/gh-issues

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add openclaw/openclaw --skill gh-issues -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw gh-issues --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gh-issues .agents/skills/gh-issues && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gh-issues" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/gh-issues into .agents/skills/gh-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-issues", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add openclaw/openclaw --skill gh-issues -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw gh-issues --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gh-issues .cursor/skills/gh-issues && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gh-issues" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/gh-issues into .cursor/skills/gh-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-issues", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/openclaw/openclaw.git --path skills/gh-issues

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add openclaw/openclaw --skill gh-issues -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw gh-issues --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gh-issues .gemini/skills/gh-issues && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gh-issues" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/gh-issues into .gemini/skills/gh-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-issues", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install openclaw/openclaw gh-issues

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add openclaw/openclaw --skill gh-issues -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gh-issues .github/skills/gh-issues && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gh-issues" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/gh-issues into .github/skills/gh-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-issues", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add openclaw/openclaw --skill gh-issues -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install openclaw/openclaw gh-issues --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gh-issues .opencode/skills/gh-issues && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gh-issues" agent skill from https://github.com/openclaw/openclaw/tree/main/skills/gh-issues into .opencode/skills/gh-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gh-issues", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gh-issues
GitHub stars: 392k
Used in: 1 other repo
Token cost: ~1.6k tokens
SKILL.md length: 464 words
Files: 1
Skills in repo: 93
Repo updated: Oct 8, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

Works in 6 steps: resolve repo → fetch issues → avoid duplicate work → …
Tasks that involve Pull requests
SKILL.md covers Arguments, Phase 1: resolve repo, Phase 2: fetch issues and Phase 3: avoid duplicate work, plus 5 more sections
Calls gh, git and jq; reaches github.com; needs GH_TOKEN

What it does

Gh Issues is an agent skill from openclaw/openclaw. Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

When your agent uses it

Tasks that involve Pull requests

Example prompts

“/gh-issues”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

resolve repo
fetch issues
avoid duplicate work
confirm
spawn workers
collect

What it can do on your machine

Read from SKILL.md and the folder at commit 1eb5970. 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
- git
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gh Issues loads about 1.6k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 464 words of instructions outside code blocks.

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

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 openclaw/openclaw at commit 1eb5970, republished under its MIT licence (© openclaw). 464 words, ~1,580 tokens.

Download SKILL.mdSave it as .claude/skills/gh-issues/SKILL.md (or your agent's skills folder).

name: gh-issues
description: Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
user-invocable: true

gh-issues

Use for issue-to-PR automation. Prefer gh CLI; fall back to gh api only when a high-level command lacks the needed field.

Arguments

positional owner/repo: optional; else infer from git remote get-url origin.
--label <label>: filter.
--limit <n>: default 10.
--milestone <title>: filter.
--assignee <login|@me>: filter.
--state open|closed|all: default open.
--fork <owner/repo>: push branches to fork, PR to source.
--watch: poll issues + reviews.
--interval <minutes>: default 5.
--dry-run: list only.
--yes: no confirmation.
--reviews-only: skip issue fixing; handle PR reviews.
--cron: spawn and exit; implies --yes.
--model <id>: pass to workers when supported.
--notify-channel <id>: optional final notification target.

Phase 1: resolve repo

bash

git remote get-url origin
if [ -z "${GH_TOKEN:-}" ]; then
  CONFIG_PATH="${OPENCLAW_CONFIG_PATH:-${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/openclaw.json}"
  GH_TOKEN=$(jq -r '.skills.entries["gh-issues"].apiKey // empty' "$CONFIG_PATH" 2>/dev/null || true)
  if [ -n "$GH_TOKEN" ]; then export GH_TOKEN; fi
fi
gh auth status
gh repo view OWNER/REPO --json nameWithOwner,defaultBranchRef

If gh auth status fails and GH_TOKEN is missing, stop and ask for GitHub auth/config.

Derived:

SOURCE_REPO: issue repo.
PUSH_REPO: fork if set, else source.
BASE_BRANCH: source default branch unless user says otherwise.
PUSH_REMOTE: fork in fork mode, else origin.

Stop on dirty worktree unless user confirms that workers should ignore uncommitted changes.

In fork mode, do not mutate remotes before confirmation or during --dry-run.

Verify auth/read access only:

bash

gh auth token >/dev/null || test -n "${GH_TOKEN:-}"
gh repo view "$PUSH_REPO" --json nameWithOwner
git ls-remote --exit-code origin HEAD

Phase 2: fetch issues

Build filters and fetch:

bash

gh issue list --repo "$SOURCE_REPO" --state open --limit 10 --json number,title,labels,url,body,assignees,milestone

Add --label, --milestone, --assignee, --state, --limit as requested. gh issue list already excludes PRs.

If none found: report no matches. If --dry-run: show compact list and stop.

Phase 3: avoid duplicate work

For each candidate:

bash

gh pr list --repo "$SOURCE_REPO" --search "$SOURCE_REPO#<n>" --state open --json number,url,title,headRefName
gh pr list --repo "$SOURCE_REPO" --head "fix/issue-<n>" --state open --json number,url
gh api "repos/$PUSH_REPO/branches/fix/issue-<n>" >/dev/null

Skip candidates with an open PR, existing branch, or active local claim.

Claim file:

text

${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/gh-issues-<owner>-<repo>.json

Expire claims older than 2 hours. Create the parent directory before writing.

Phase 4: confirm

Unless --yes or --cron, ask user to choose:

all
comma-separated issue numbers
cancel

After confirmation, in fork mode, configure the push remote before handing work to agents:

bash

gh auth setup-git
git remote get-url fork || git remote add fork "https://github.com/$PUSH_REPO.git"
git remote set-url fork "https://github.com/$PUSH_REPO.git"
git ls-remote --exit-code fork HEAD

Show full SKILL.md (193 more words)Show less

Phase 5: spawn workers

Launch up to 8 background workers. Do not block on each worker when --cron.

Before each spawn, write a claim for SOURCE_REPO#<n> with the current ISO timestamp. After a worker reports PR/failure, remove or update the claim. This prevents watch/cron overlap before a branch or PR exists.

Worker prompt must include:

issue URL, title, body, labels.
SOURCE_REPO, PUSH_REPO, BASE_BRANCH, PUSH_REMOTE, fork mode.
target branch fix/issue-<n>.
required proof and PR body.
notification route.

Worker instructions:

text

Use gh and git. Do not handwave.
Checkout/create fix/issue-<n> from BASE_BRANCH.
Implement minimal fix.
Run relevant tests.
Commit with conventional message.
Push to PUSH_REMOTE.
Open PR against SOURCE_REPO BASE_BRANCH.
PR body: What Problem This Solves + Why This Change Was Made + User Impact + Evidence + visible Fixes SOURCE_REPO#<n>.
Report PR URL or failure reason.
Send completion/failure with openclaw message send if route provided.

Use coding-agent launch rules when available.

Phase 6: collect

Poll workers with process or task registry. Report:

issue number + title.
status: PR opened, skipped, failed, timed out.
PR URL or reason.

Notify channel only with final compact summary.

Reviews-only / watch reviews

Discover open PRs:

bash

gh pr list --repo "$SOURCE_REPO" --state open --json number,title,url,headRefName,reviewDecision \
  --jq '[.[] | select(.headRefName | startswith("fix/issue-"))]'

Fetch review threads/comments:

bash

gh pr view <n> --repo "$SOURCE_REPO" --json url,headRefName,comments,reviews
gh api "repos/$SOURCE_REPO/pulls/<n>/comments"
gh api "repos/$SOURCE_REPO/issues/<n>/comments"

Only process fix/issue-* PRs created by this workflow unless the user explicitly named PR numbers. Group actionable comments by PR. Ignore praise, status, duplicates, and already-addressed comments. Spawn one worker per selected/scoped PR, same background rules.

Review worker instructions:

text

Checkout PR branch.
Read all actionable review comments.
Patch minimal changes.
Run relevant tests.
Commit and push normally; do not force-push unless explicitly told.
Reply to addressed comments with fix + commit/file reference.
Report comments addressed/skipped and proof.

Watch mode

Loop:

Fetch issues.
Spawn eligible issue workers.
Process actionable PR reviews.
Sleep --interval.
Stop when user says stop.

Keep cumulative summary small.

Files

Just SKILL.md in skills/gh-issues of openclaw/openclaw.

Open the folder on GitHubat commit 1eb5970

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in openclaw/openclaw, which our catalogue first saw on October 8, 2026.

Kevin100202/Rocket-Design-and-Manufacturing-Automation-Program-from-Shenzhen22highschoolskills/gh-issues

Compare with similar skills

Gh Issues 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.

Gh Issues compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gh Issues this skillopenclaw/openclaw	392k	1 repos	~1.6k	Automated safety check: Pass	MIT	today
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	yesterday
Check PRonyx-dot-app/onyx	32k	2 repos	~2.3k	Automated safety check: Pass	MIT	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday

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

Questions about Gh Issues

What does Gh Issues do?

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments. Gh Issues is an agent skill from openclaw/openclaw. Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

When should I use Gh Issues?

Gh Issues fits situations like: tasks that involve Pull requests.

How do I install Gh Issues in Claude Code?

Run `npx skills add openclaw/openclaw --skill gh-issues -a claude-code`. Or copy the skill folder (skills/gh-issues in openclaw/openclaw) into .claude/skills/gh-issues in your project. Claude Code loads it when a task matches its description.

How do I install Gh Issues in Codex?

Run `npx skills add openclaw/openclaw --skill gh-issues -a codex`. Or copy the skill folder (skills/gh-issues in openclaw/openclaw) into .agents/skills/gh-issues in your project. Codex loads it when a task matches its description.

Can I use Gh Issues 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 openclaw/openclaw --skill gh-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-issues, .gemini/skills/gh-issues, .github/skills/gh-issues and .opencode/skills/gh-issues in your project.

What does Gh Issues need to run?

Going by SKILL.md and its folder, Gh Issues needs the command-line tools its instructions call (gh, git and jq) and credentials named GH_TOKEN.

Does Gh Issues access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Gh Issues 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 Gh Issues use?

Gh Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gh Issues use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 Gh Issues?

Skills that share tags, products or a category with Gh Issues: 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 Gh Issues?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,610 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Gh Issues

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

gh-issues

Arguments

Phase 1: resolve repo

Phase 2: fetch issues

Phase 3: avoid duplicate work

Phase 4: confirm

Phase 5: spawn workers

Phase 6: collect

Reviews-only / watch reviews

Watch mode

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from openclaw/openclaw

Related

Questions about Gh Issues