gh-issues

What it does

Fetch GitHub issues for a repository, spawn sub-agents to implement fixes and open PRs, and then monitor PR reviews. Supports optional fork mode, polling, dry-run, confirmation, cron mode, and notifications via a channel.

How it works

• Parses arguments after /gh-issues to determine SOURCE_REPO, PUSH_REPO, and flags (labels, limit, milestone, assignee, state, fork, watch, interval, dry-run, yes, reviews-only, cron, model, notify-channel).
• Phase 2 fetches issues from the GitHub REST API using curl with a Bearer GH_TOKEN, applying filters for label, milestone, and assignee, removing pull requests from results, and handling watch mode.
• Phase 3 presents a markdown table of issues and, depending on modes (--dry-run or --yes), either confirms processing or asks for user input to select issues to process. In watch mode, confirmation is required on the first poll.
• Phase 4 performs pre-flight checks: dirty working tree, base branch, remote access (fork vs origin), GH_TOKEN validity, existing PRs, in-progress branches on the push repo, and claim-based in-progress tracking. Skips issues with existing PRs or branches, or those claimed recently.
• Phase 5 spawns sub-agents in parallel (normal mode) or sequentially (cron mode). Each spawn includes optional model and notify-channel, writes a claim timestamp, and exits without awaiting results. In cron mode, a cursor tracks the next issue; in normal mode, up to 8 concurrent sub-agents are spawned, batching as needed.
• Sub-agent task prompts are constructed with issue details and environment values, and all GitHub operations use curl with Authorization: Bearer $GH_TOKEN. After spawning, a claim is written and a short confirmation is emitted.

When to use it

• Use when you want to automatically fetch issues, create targeted fixes via sub-agents, and manage PR creation and review, optionally in a forked workflow and with periodic polling (--watch).
• Activate cron mode for scheduled, non-blocking runs that exit after spawning; use --cron with --yes or --reviews-only to tailor behavior.

What it can touch

• GitHub via REST API: issues, milestones, users, pulls, branches creation, and PRs.
• Local git repository for remote checks and push/fork configuration when not in cron mode.
• A claims file at /data/.clawdbot/gh-issues-claims.json to track in-progress or claimed issues.
• Cursor and staging files at /data/.clawdbot used for cron mode sequencing.

Caveats

• Requires GH_TOKEN to be available as an Authorization Bearer token for API calls; misconfiguration yields authentication errors.
• Does not use gh CLI; relies entirely on curl + GitHub REST API.
• Behavior depends on mode: cron mode is sequential with a cursor; normal mode spawns multiple sub-agents concurrently and updates claims.
• Some steps assume an OpenClaw/OpenClaw-provided environment and filesystem paths; behavior may vary outside that environment.