What is github-issue-solve?

A workflow for turning a GitHub issue, a tracked software task or bug, into a code change and pull request.

Use it to collect issue details, implement a fix, and open or update a pull request.

It connects the issue's requirements, implementation work, and proposed change so the fix can be delivered in one process.

github-issue-solve — Skill by holon-run

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/holon-run/holon/github-issue-solve

Any agent

npx skills add holon-run/holon --skill github-issue-solve

Clone the repo

git clone --depth 1 https://github.com/holon-run/holon

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 844 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00027	$0.00844
Opus 5	$0.00014	$0.00422
Sonnet 5	$0.00005	$0.00169
Haiku 4.5	$0.00003	$0.00084

Measured 2d ago against content hash c4d5c8913b6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-issue-solve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/github-issue-solve/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Issue Solve Skill

Summary

Use this skill when you need to turn a GitHub issue into a concrete code change and publish the result as a pull request.

When To Use

Fixing a GitHub issue end-to-end
Collecting issue context and comments with raw gh commands
Implementing code changes and opening or updating a PR

Do Not Use

Reviewing an existing PR without making changes
Replying to review feedback on an existing PR
Project-wide planning or backlog triage

Prerequisites

gh CLI authentication is required.
GITHUB_TOKEN/GH_TOKEN must allow issue/PR read-write operations.

Runtime Paths

GITHUB_OUTPUT_DIR: output artifacts directory (caller-provided preferred; otherwise temp dir).
GITHUB_CONTEXT_DIR: context directory (default ${GITHUB_OUTPUT_DIR}/github-context).

Inputs (Manifest-First)

Preferred input when already available:

${GITHUB_CONTEXT_DIR}/manifest.json

Optional inputs:

Any artifact listed as status=present in manifest.artifacts[].

If no manifest is provided, collect issue metadata and comments directly with gh:

gh issue view <issue_number> --repo <owner/repo> --json number,title,body,state,url,author,createdAt,updatedAt,labels
gh api repos/<owner>/<repo>/issues/<issue_number>/comments --paginate

Do not assume fixed file names under github/. Resolve usable inputs from manifest.artifacts[] by id/path/status/description.

Workflow

1. Collect context

If ${GITHUB_CONTEXT_DIR}/manifest.json exists, use it.
Otherwise, collect the issue body and comments directly with gh.

2. Analyze and implement

Extract acceptance criteria and constraints from issue metadata and discussion.
Implement minimal complete changes for the requested outcome.
Use deterministic branch naming (feature/issue-<number> or fix/issue-<number>).
Run relevant verification commands before publish.

3. Commit and push

Commit only intentional changes.
Push branch to remote before PR publish.

Read the full file on GitHub · 123 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/issue-solve-workflow.md 1.6 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 123 lines · 27 tokens per session scan A c4d5c8913b6f

Subscribe to this mod's changes

github-issue-solve is a skill published in the GitHub repository holon-run/holon (134 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 844 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Debugging Planning agent-runtime ai-agents ai-infrastructure developer-tools local-first

github-issue-solve