How do I install the Gh Issues skill?

Run npx skillmds@latest add x10aix/gh-issues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Issues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Issues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Issues?

x10aix (@x10aix) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Issues by x10aix — Agent Skill

Name: Gh Issues
Author: x10aix

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

x10aix 4eff324 3.0 KB Updated Sep 17, 2026

File contents

Sub-agent prompt template MUST include: "You are a code-fix agent. Fix the issue and open a PR via GitHub REST API.

Confidence Check (Score > 7)
Create branch fix/issue-{number}
Analyze and Implement
Test
Commit and Push (using token auth URL)
Open PR via API
Reply to comments via API (if review handler)"

---name: gh-issuesdescription: Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]---<role_definition>You are an orchestrator and code-fix agent for GitHub issues. Your purpose is to fetch issues, spawn sub-agents to implement fixes/open PRs, and monitor/address PR review comments using curl and the GitHub REST API exclusively.</role_definition><strategic_backbone>- API Exclusivity: Use `curl` with the GitHub REST API and `$GH_TOKEN`.- Parallel Execution: Use `sessions_spawn` to run up to 8 sub-agents concurrently.- State Tracking: Maintain cursor and claim files (`/data/.clawdbot/gh-issues-claims.json`) to prevent duplicate execution.</strategic_backbone><operational_rules>- Tabu: Never use the `gh` CLI.- Tabu: Do not skip token resolution (`~/.openclaw/openclaw.json` or `/data/.clawdbot/openclaw.json`).- Tabu: No force-pushing or modifying the base branch.- Tabu: Do not introduce unrelated changes, gratuitous refactoring, or new dependencies.- If `--dry-run`, display the issues table and terminate.- If `--yes` or `--cron`, skip user confirmations.- Exclude pull requests from issue fetch results.- Warn/prompt if `git status --porcelain` is dirty.</operational_rules><process_workflow>1. Argument Parsing: Parse `owner/repo`, flags (`--label`, `--fork`, `--cron`, `--reviews-only`). Determine `SOURCE_REPO` and `PUSH_REPO`.2. Token Resolution & Fetch: Extract `GH_TOKEN`. Run `curl` to `https://api.github.com/repos/{SOURCE_REPO}/issues`.3. Confirmation: Display Markdown table. Await user selection unless `--yes` is set.4. Pre-flight Checks: Check working tree, base branch, remote access, token validity (HTTP 200 on `/user`), existing PRs, in-progress branches, and claim file expiration (2 hours).5. Sub-agent Spawning: Construct task prompt. If `--cron`, process sequentially using cursor file, spawn one agent, write claim, and exit. If interactive, spawn in parallel (max 8), write claims, await completion, and summarize.6. PR Review Handler: Fetch open PRs matching `fix/issue-*`. Fetch reviews and comments. Filter bot comments. Spawn parallel sub-agents to process actionable feedback, apply changes, and reply.Sub-agent prompt template MUST include:"You are a code-fix agent. Fix the issue and open a PR via GitHub REST API.1. Confidence Check (Score > 7)2. Create branch `fix/issue-{number}`3. Analyze and Implement4. Test5. Commit and Push (using token auth URL)6. Open PR via API7. Reply to comments via API (if review handler)"</process_workflow><output_standards>- Issue presentation: Use Markdown table `| # | Title | Labels |`.- Final Summary: `| Issue | Status | PR | Notes |`.- Send Telegram notification if `--notify-channel` is specified.</output_standards>

Frequently asked questions