gh-issues

Automates GitHub issue triage, background fix agents, and pull request creation via gh CLI.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill gh-issues-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/skills/gh-issues
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill gh-issues-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually triaging GitHub issues, writing fixes, opening pull requests, and responding to review comments is repetitive and time-consuming. This Skill automates the entire issue-to-PR pipeline so fixes are proposed without constant human involvement. ## Core Features & Use Cases - Issue Fetching and Filtering: List open issues by label, milestone, assignee, state, and limit using the GitHub CLI. - Background Fix Workers: Spawn up to 8 parallel agents that create fix branches, implement minimal changes, run tests, and open PRs with conventional commit messages. - Duplicate Prevention: Skip issues that already have open PRs, existing branches, or active claims to avoid overlapping work. - Review Comment Processing: Detect actionable review comments on generated PRs and spawn workers to address them. - Use Case: Run the skill in watch mode against a repository to continuously pick up new labeled issues, open fix PRs, and respond to reviewer feedback automatically. ## Quick Start Ask the assistant to fetch open issues from the current repository, pick candidates, and open fix pull requests for them.

Frequently Asked Questions about gh-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically create pull requests from GitHub issues?

Use the gh CLI to list open issues with filters like label or milestone, then spawn background workers that create fix branches, implement changes, run tests, and open PRs against the base branch. Each PR body includes a summary, verification steps, and a Fixes reference to the issue.

How to filter GitHub issues by label or assignee with gh CLI?

Pass --label, --milestone, --assignee, --state, and --limit flags to gh issue list. The command returns JSON with number, title, labels, url, body, assignees, and milestone, and it already excludes pull requests from results.

Can I push fix branches to a fork and PR to the original repo?

Yes, fork mode pushes branches to a specified fork while opening PRs against the source repository. The workflow configures a fork remote with gh auth setup-git and verifies access before spawning any workers.

How does the workflow avoid duplicate PRs for the same issue?

Before spawning a worker, it checks for open PRs referencing the issue, existing fix/issue-N branches, and active local claim files. Claims older than two hours expire, preventing overlap between watch and cron runs.

What happens when gh auth fails or GH_TOKEN is missing?

The workflow stops and asks for GitHub authentication or configuration. It first attempts to read a token from the OpenClaw config file, then verifies access with gh auth status and gh repo view before proceeding.

Can it respond to PR review comments automatically?

Yes, reviews-only mode fetches review threads and comments on fix/issue-* PRs, groups actionable feedback, and spawns workers that patch changes, run tests, push commits, and reply to addressed comments with commit references.