gh-issues

Automates GitHub issue fixes by spawning sub-agents that create PRs and address review comments.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/srgaba/open-claw --skill gh-issues-srgaba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/srgaba/open-claw/tree/main/project/skills/gh-issues
Command: npx skills add https://github.com/srgaba/open-claw --skill gh-issues-srgaba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually triaging GitHub issues, writing fixes, opening pull requests, and responding to review feedback is repetitive and time-consuming. This Skill automates the entire loop: it fetches issues from a repository, delegates fixes to parallel sub-agents, opens PRs, and continuously monitors and addresses PR review comments. ## Core Features & Use Cases - Automated Issue Fixing: Fetches open issues via the GitHub REST API (with label, milestone, assignee, and state filters) and spawns up to 8 parallel sub-agents that branch, implement, test, commit, and open PRs. - PR Review Handling: Monitors open fix/issue-* PRs for review comments (including inline comments and embedded bot reviews like Greptile), then spawns agents to implement requested changes and reply to reviewers. - Fork & Watch Modes: Supports pushing branches to a fork while targeting PRs at the upstream repo, plus watch mode for continuous polling and cron mode for scheduled fire-and-forget runs. - Use Case: Run /gh-issues myorg/myrepo --label bug --limit 5 --watch to continuously pick up new bug reports, auto-fix them, open PRs, and respond to reviewer feedback without manual intervention. ## Quick Start Ask the agent to run /gh-issues on your repository, for example: fetch open bug issues from owner/repo, fix them with sub-agents, and open pull requests.

Frequently Asked Questions about gh-issues

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

FAQPage Schema
How do I automatically fix GitHub issues with AI agents?

Run /gh-issues with a target repository, and the skill fetches open issues via the GitHub REST API, then spawns parallel sub-agents that create branches, implement fixes, run tests, and open pull requests. Use flags like --label and --limit to control which issues are processed.

How do I respond to GitHub PR review comments automatically?

Use the --reviews-only flag to skip issue processing and only monitor open fix/issue-* PRs. The skill fetches reviews, inline comments, and embedded bot feedback, identifies actionable items, and spawns agents to implement the requested changes and reply to reviewers.

Does this skill require the GitHub CLI (gh)?

No, the skill explicitly avoids the gh CLI and uses curl with the GitHub REST API for all operations. It only requires curl, git, and a GH_TOKEN environment variable for authentication.

Can I open PRs from a fork instead of the source repository?

Yes, pass --fork user/repo to push branches to your fork while issues are fetched from the source repo. PRs are then opened from the fork's branch to the source repository's base branch.

What happens if a fix already has an open PR or branch?

Pre-flight checks detect existing open PRs, existing fix/issue-* branches on the push repo, and recent claim records from prior runs. Matching issues are skipped to avoid duplicate work, and expired claims older than two hours are cleaned up.

Why would a sub-agent skip fixing an issue?

Sub-agents perform a confidence check before implementing. If the issue is vague, the relevant code cannot be located, or the scope is too large, the agent rates confidence below 7 and reports a skip reason instead of guessing at a fix.