MyClawMyClaw
HomeUse CasesPricingSkillsResourcesCompany
HomeUse CasesPricingSkills
Sign In
HomeUse CasesPricingSkills
ResourcesCompareBlogCommunity
CompanyAboutSupport
Sign In
MyClawMyClaw

Your AI agent, already running.

Product

OpenClaw HostingHermes Agent HostingSlackUse CasesPricingAlibaba Cloud

Tools

Passport Photo GeneratorTattoo DesignVirtual Background GeneratorLinkedIn Headshot GeneratorParty Invitation GeneratorAlbum Cover GeneratorDating Photo Generator

Compre

vs dotsvs Claudevs ChatGPTvs OpenClawvs Hermes Agentvs Grok Botvs Hostinger

Resources

BlogUpdatesSkillsModelsSupportCommunityCapybara

© 2023 Cubo World Inc. All rights reserved.

TermsPrivacyCookieGDPRContact
← Back to Skills
Coding Agents & IDEs
⌨️

gh-issues

Auto-fix GitHub issues using parallel AI sub-agents that implement changes, open PRs, and respond to code review feedback.

by OpenClawv1.0.0
ProductivityAI PoweredOpen SourceAutomationAPIDeveloper Tool
Connecting to VM...
Connecting to VM...
npx clawhub@latest install gh-issues
33Current Installs
📦
v1.0.0Version

Requirements

curlgitghGitHub Token

gh-issues Skill Overview

gh-issues is an AI orchestration skill that turns your GitHub issue backlog into merged pull requests with minimal human intervention. Given a repository, it fetches open issues, spawns parallel sub-agents to analyze and implement fixes, pushes branches, opens PRs, and then monitors those PRs for review comments — spawning additional agents to address feedback. It supports fork workflows, watch/polling mode, cron scheduling, Telegram notifications, and configurable model selection.

How to Use It

Step 1: Run in your terminal or install this skill on MyClaw

npx clawhub@latest install gh-issues
or

Click the Install button at the top of this page for one-click setup

When to Use gh-issues

Best Fit

  • You have a backlog of clearly-scoped bug issues and want a first-pass automated fix attempt before human review.
  • You run a scheduled CI/cron pipeline and want issues automatically triaged and PRed without manual intervention (--cron mode).
  • You work with a fork-based contribution model and need branches pushed to your fork with PRs targeting an upstream repo (--fork).
  • You want PR review comments addressed automatically — use --reviews-only to have the skill scan open fix/issue-* PRs and push fixes for requested changes.

When Not to Use

  • Issues are vague, architectural, or large in scope — the skill's sub-agents self-assess confidence and will skip issues they rate below 7/10, but highly complex issues should be handled manually.
  • You need guaranteed correctness — sub-agents run tests when available, but auto-generated fixes should be reviewed before merging into production.
  • You have no GitHub token (GH_TOKEN) — the skill cannot authenticate to any GitHub API without it.

Key Features

Parallel Sub-agent Issue Processing

Up to 8 sub-agents run concurrently, each tackling a single issue end-to-end: branch creation, code analysis, fix implementation, test execution, commit, push, and PR opening. Each agent has a 60-minute budget and a built-in confidence check — it skips issues it cannot address with ≥7/10 confidence.

Automated PR Review Response

After PRs are opened, Phase 6 fetches reviews, inline comments, general PR comments, and even embedded bot reviews (e.g., Greptile). Actionable comments trigger additional sub-agents that check out the branch, apply the requested changes, push an update, and reply to each comment with the commit SHA.

Fork Mode Support

Pass --fork user/repo to push all branches to your fork and open PRs from the fork targeting the upstream source repository — matching the standard open-source contribution workflow without requiring write access to the upstream.

Cron & Watch Modes

--cron enables fire-and-forget scheduling: the orchestrator picks one eligible issue, spawns a sub-agent, and exits immediately — safe to call from a cron job every few minutes. --watch keeps the orchestrator alive, polling for new issues and review comments on a configurable interval.

Duplicate & In-Progress Prevention

Before spawning, the skill checks for existing open PRs, in-progress branches on the push repo, and a local claims file with 2-hour expiry. This prevents duplicate sub-agents from racing on the same issue across overlapping cron runs or watch cycles.

Telegram Notifications

Pass --notify-channel with a Telegram channel ID to receive a final summary message containing PR links and per-issue results. Only the final outcome is sent — not intermediate status updates.

Use Cases

Automated bug-fix pipeline for a public OSS repo

Run /gh-issues owner/repo --label bug --limit 10 --cron from a scheduled job. Each invocation picks the next unclaimed bug issue, spawns a sub-agent to implement a fix, and exits. Over time, the backlog is worked through incrementally without human involvement between runs.

Fork-based contribution to an upstream project

Use /gh-issues upstream/project --fork myfork/project --label good-first-issue to have the skill fetch issues from the upstream repo, push fix branches to your fork, and open PRs targeting upstream — respecting the standard contributor workflow.

Continuous PR review response

Schedule /gh-issues owner/repo --reviews-only --cron alongside your existing PR pipeline. Each run scans open fix/issue-* PRs for unaddressed CHANGES_REQUESTED reviews or inline comments, picks the first unhandled PR, and spawns an agent to apply the requested changes and reply.

Interactive triage session with watch mode

Run /gh-issues owner/repo --label enhancement --watch --interval 10 during a sprint planning session. The skill fetches issues, asks you to confirm which to process, spawns agents, and polls every 10 minutes for new issues and review feedback — presenting cumulative results until you say 'stop'.

Requirements

  • GitHub Token (required) — Authenticates all GitHub REST API calls. Set as GH_TOKEN in your environment or configure under skills.entries["gh-issues"].apiKey in the OpenClaw dashboard / ~/.openclaw/openclaw.json.
  • Telegram Bot (optional) — Required only if using --notify-channel. The OpenClaw agent must have access to a configured Telegram bot capable of sending messages to the target channel.
Connecting to VM...
npx clawhub@latest install gh-issues
33Current Installs
📦
v1.0.0Version

Requirements

curlgitghGitHub Token

FAQ

Reviews

0 reviews

Log in to write a review

No reviews yet. Be the first to share your experience!