gh-issues

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

You say
Buy it · $24 Read it before you buy $24 Written by openclaw · unverified publisher
Context cost
1.6k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 6.3 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Guardrail

Constrains what the agent is allowed to do.

collaborationgithub

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.3 kB · 214 lines
--- name: gh-issues description: "Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments." user-invocable: true metadata: { "openclaw": { "requires": { "bins": ["git", "gh"] }, "primaryEnv": "GH_TOKEN", "install": [ { "id": "brew", "kind": "brew", "formula": "gh", "bins": ["gh"], "label": "Install GitHub CLI (brew)", }, ], }, } ---
25# gh-issues
26
27Use for issue-to-PR automation. Prefer gh CLI; fall back to gh api only when a high-level command lacks the needed field.
28
29## Arguments
30
31- positional owner/repo: optional; else infer from git remote get-url origin.
32- --label <label>: filter.
33- --limit <n>: default 10.
34- --milestone <title>: filter.
35- --assignee <login|@me>: filter.
36- --state open|closed|all: default open.
37- --fork <owner/repo>: push branches to fork, PR to source.
38- --watch: poll issues + reviews.
39- --interval <minutes>: default 5.
40- --dry-run: list only.
41- --yes: no confirmation.
42- --reviews-only: skip issue fixing; handle PR reviews.
43- --cron: spawn and exit; implies --yes.
44- --model <id>: pass to workers when supported.
45- --notify-channel <id>: optional final notification target.
46
47## Phase 1: resolve repo
48
49```bash
50git remote get-url origin
51if [ -z "${GH_TOKEN:-}" ]; then
52 CONFIG_PATH="${OPENCLAW_CONFIG_PATH:-${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/openclaw.json}"
53 GH_TOKEN=$(jq -r '.skills.entries["gh-issues"].apiKey // empty' "$CONFIG_PATH" 2>/dev/null || true)
54 if [ -n "$GH_TOKEN" ]; then export GH_TOKEN; fi
55fi
56gh auth status
57gh repo view OWNER/REPO --json nameWithOwner,defaultBranchRef
58```
59
60If gh auth status fails and GH_TOKEN is missing, stop and ask for GitHub auth/config.
61
62Derived:
63
64- SOURCE_REPO: issue repo.
65- PUSH_REPO: fork if set, else source.
66- BASE_BRANCH: source default branch unless user says otherwise.
67- PUSH_REMOTE: fork in fork mode, else origin.
68
69Stop on dirty worktree unless user confirms that workers should ignore uncommitted changes.
70
71In fork mode, do not mutate remotes before confirmation or during --dry-run.
72
73Verify auth/read access only:
74
75```bash
76gh auth token >/dev/null || test -n "${GH_TOKEN:-}"
77gh repo view "$PUSH_REPO" --json nameWithOwner
78git ls-remote --exit-code origin HEAD
79```
80
81## Phase 2: fetch issues
82
83Build filters and fetch:
84
85```bash
86gh issue list --repo "$SOURCE_REPO" --state open --limit 10 --json number,title,labels,url,body,assignees,milestone
87```
88
89Add --label, --milestone, --assignee, --state, --limit as requested. gh issue list already excludes PRs.
90
91If none found: report no matches. If --dry-run: show compact list and stop.
92
93## Phase 3: avoid duplicate work
94
95For each candidate:
96
97```bash
98gh pr list --repo "$SOURCE_REPO" --search "$SOURCE_REPO#<n>" --state open --json number,url,title,headRefName
99gh pr list --repo "$SOURCE_REPO" --head "fix/issue-<n>" --state open --json number,url
100gh api "repos/$PUSH_REPO/branches/fix/issue-<n>" >/dev/null
101```
102
103Skip candidates with an open PR, existing branch, or active local claim.
104
105Claim file:
106
107```text
108${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/gh-issues-<owner>-<repo>.json
109```
110
111Expire claims older than 2 hours.
112Create the parent directory before writing.
113
114## Phase 4: confirm
115
116Unless --yes or --cron, ask user to choose:
117
118- all
119- comma-separated issue numbers
120- cancel
121
122After confirmation, in fork mode, configure the push remote before handing work to agents:
123
124```bash
125gh auth setup-git
126git remote get-url fork || git remote add fork "https://github.com/$PUSH_REPO.git"
127git remote set-url fork "https://github.com/$PUSH_REPO.git"
128git ls-remote --exit-code fork HEAD
129```
130
131## Phase 5: spawn workers
132
133Launch up to 8 background workers. Do not block on each worker when --cron.
134
135Before each spawn, write a claim for SOURCE_REPO#<n> with the current ISO timestamp. After a worker reports PR/failure, remove or update the claim. This prevents watch/cron overlap before a branch or PR exists.
136
137Worker prompt must include:
138
139- issue URL, title, body, labels.
140- SOURCE_REPO, PUSH_REPO, BASE_BRANCH, PUSH_REMOTE, fork mode.
141- target branch fix/issue-<n>.
142- required proof and PR body.
143- notification route.
144
145Worker instructions:
146
147```text
148Use gh and git. Do not handwave.
149Checkout/create fix/issue-<n> from BASE_BRANCH.
150Implement minimal fix.
151Run relevant tests.
152Commit with conventional message.
153Push to PUSH_REMOTE.
154Open PR against SOURCE_REPO BASE_BRANCH.
155PR body: What Problem This Solves + Why This Change Was Made + User Impact + Evidence + visible Fixes SOURCE_REPO#<n>.
156Report PR URL or failure reason.
157Send completion/failure with openclaw message send if route provided.
158```
159
160Use coding-agent launch rules when available.
161
162## Phase 6: collect
163
164Poll workers with process or task registry. Report:
165
166- issue number + title.
167- status: PR opened, skipped, failed, timed out.
168- PR URL or reason.
169
170Notify channel only with final compact summary.
171
172## Reviews-only / watch reviews
173
174Discover open PRs:
175
176```bash
177gh pr list --repo "$SOURCE_REPO" --state open --json number,title,url,headRefName,reviewDecision \
178 --jq '[.[] | select(.headRefName | startswith("fix/issue-"))]'
179```
180
181Fetch review threads/comments:
182
183```bash
184gh pr view <n> --repo "$SOURCE_REPO" --json url,headRefName,comments,reviews
185gh api "repos/$SOURCE_REPO/pulls/<n>/comments"
186gh api "repos/$SOURCE_REPO/issues/<n>/comments"
187```
188
189Only process fix/issue-* PRs created by this workflow unless the user explicitly named PR numbers. Group actionable comments by PR. Ignore praise, status, duplicates, and already-addressed comments. Spawn one worker per selected/scoped PR, same background rules.
190
191Review worker instructions:
192
193```text
194Checkout PR branch.
195Read all actionable review comments.
196Patch minimal changes.
197Run relevant tests.
198Commit and push normally; do not force-push unless explicitly told.
199Reply to addressed comments with fix + commit/file reference.
200Report comments addressed/skipped and proof.
201```
202
203## Watch mode
204
205Loop:
206
2071. Fetch issues.
2082. Spawn eligible issue workers.
2093. Process actionable PR reviews.
2104. Sleep --interval.
2115. Stop when user says stop.
212
213Keep cumulative summary small.
214
In the file
SKILL.md835 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈140
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,435
on trigger
The instruction body, read only when the skill fires.
0.79%
of a 200k window
Ten skills this size would take about 8% of the window before you open a file.
050k100k150k200k context window

1.6k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 6.3 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md6.3 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$24 once
gh-issues · MIT · openclaw
one-time
Price$24 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$24
Referenceopenclaw/gh-issues

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0