Agent skill · Code Review & Quality

gh-issues

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

Health-Yanggithub.com/Health-YangGitHub ↗
claude-codeNOASSERTION
Install
npx skills add Health-Yang/MineEcho --skill gh-issues --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: vendor/openclaw-gateway/skills/gh-issues/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 248
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 nameWithOwne

What's inside
Steps it walks through
  1. Arguments
  2. Phase 1: resolve repo
  3. Phase 2: fetch issues
  4. Phase 3: avoid duplicate work
  5. Phase 4: confirm
  6. Phase 5: spawn workers
  7. Phase 6: collect
  8. Reviews-only / watch reviews
  9. Watch mode
Commands it runs
git remote get-url origin
if [ -z "${GH_TOKEN:-}" ]; then
if [ -n "$GH_TOKEN" ]; then export GH_TOKEN; fi
fi
gh auth status
gh repo view OWNER/REPO --json nameWithOwner,defaultBranchRef
gh auth token >/dev/null || test -n "${GH_TOKEN:-}"
gh repo view "$PUSH_REPO" --json nameWithOwner
git ls-remote --exit-code origin HEAD
gh issue list --repo "$SOURCE_REPO" --state open --limit 10 --json number,title,labels,url,body,assignees,milestone
More from MineEcho
All skills →
About this skill
What does the gh-issues skill do?

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

How do I install it?

Run `npx skills add Health-Yang/MineEcho --skill gh-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Health-Yang/MineEcho, a repository with 248 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going