New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitHub Issue Solve

by holon-run in holon-run/holon

Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request.

Apache-2.0Auto-check passedDevelopment

Install GitHub Issue Solve

skills CLI
$ npx skills add holon-run/holon --skill github-issue-solve -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install holon-run/holon github-issue-solve --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/holon-run/holon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-issue-solve .claude/skills/github-issue-solve && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-issue-solve
GitHub stars
152
Token cost
~912 tokens
SKILL.md length
414 words
Files
2 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request.

  • Works in 5 steps: Collect context → Analyze and implement → Commit and push → …
  • Tasks that involve Pull requests
  • SKILL.md covers Summary, When To Use, Do Not Use and Prerequisites, plus 5 more sections
  • Calls gh; needs GITHUB_TOKEN and GH_TOKEN

What it does

GitHub Issue Solve is an agent skill from holon-run/holon. Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/issue-solve-workflow.md`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: An agent workbench for ongoing work: preserve goals and progress, connect events and schedules, and resume when the next condition is met. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/github-issue-solve”

Requirements

  • A credential in GITHUB_TOKEN

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Collect context
  2. Analyze and implement
  3. Commit and push
  4. Publish PR
  5. Finalize delivery

What it can do on your machine

Read from SKILL.md and the folder at commit a8e0887. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN
    • GH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Issue Solve loads about 912 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 31 tokens; SKILL.md has 414 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~912
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from holon-run/holon at commit a8e0887, republished under its Apache-2.0 licence (© holon-run). 414 words, ~912 tokens.

Download SKILL.mdSave it as .claude/skills/github-issue-solve/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
github-issue-solve
description
Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request.

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: optional caller-provided output artifacts directory.
  • GITHUB_CONTEXT_DIR: context directory (default ${GITHUB_OUTPUT_DIR}/github-context).
  • Do not create fixed output files unless the caller or an integration explicitly requires them.

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:

bash
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.
  • Follow the developer agent's recorded worktree, branch, and PR preferences; ask the operator when a relevant preference is not recorded.
  • Run relevant verification commands before publish.
3. Commit and push
  • Commit only intentional changes.
  • Push branch to remote before PR publish.
Show full SKILL.md (169 more words)Show less
4. Publish PR

Use raw gh commands. Pass the PR body directly, or use a caller-requested body file when the integration needs one:

bash
gh pr create --repo <owner/repo> --title "<title>" --body "<body>" --head <branch> --base <base>
gh pr edit <pr_number> --repo <owner/repo> --title "<title>" --body "<body>"

Publish completion is mandatory; do not report success without a real PR side effect.

5. Finalize delivery

Report the result in the normal agent delivery. If a caller explicitly requires machine-readable output, write only the requested artifacts under ${GITHUB_OUTPUT_DIR} and include their paths in the delivery.

Delivery Standards

  • Keep scope aligned with issue intent; avoid unrelated refactors.
  • State assumptions explicitly when requirements are ambiguous.
  • Include concrete verification results (commands + outcomes).
  • If full verification is impossible, report what was attempted and why it is incomplete.

Failure Rules

Mark run as failed if any of the following is true:

  • no meaningful code change was produced for the issue intent
  • commit/push was not completed
  • PR create/update failed or PR URL cannot be verified

Do not report success from artifacts alone. A summary or manifest is optional evidence, not a substitute for the actual commit, push, or PR side effect.

© holon-run, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/github-issue-solve of holon-run/holon.

  • SKILL.md
  • references/issue-solve-workflow.md

Open the folder on GitHubat commit a8e0887

Compare with similar skills

GitHub Issue Solve next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Issue Solve compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issue Solve this skillholon-run/holon152—~912Automated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from holon-run/holon

All 13 skills in this repo

  • Video Production

    holon-run/holon

    Assemble existing local images, videos, audio and subtitles into preview/final videos with FFmpeg, technical QC and provenance.

    152 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • GitHub PR Fix

    holon-run/holon

    Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies.

    152 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Code Health Audit

    holon-run/holon

    Audit code-health and technical-debt signals with evidence, rank proportionate interventions from focused cleanup to broad coordinated refactors, and draft implementation-ready plans without…

    152 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Code Review

    holon-run/holon

    Review a set of code changes using evidence-backed findings, explicit confidence, and a clear coverage summary.

    152 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Ghx

    holon-run/holon

    Guidance for safe, reliable GitHub CLI workflows across issues, pull requests, and reviews.

    152 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • GitHub Review

    holon-run/holon

    Review a GitHub pull request by collecting GitHub context, applying evidence-backed review rules, and optionally publishing one review.

    152 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about GitHub Issue Solve

What does GitHub Issue Solve do?

Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request. GitHub Issue Solve is an agent skill from holon-run/holon. Solve a GitHub issue by collecting context, implementing a fix, and opening or updating a pull request.

When should I use GitHub Issue Solve?

GitHub Issue Solve fits situations like: tasks that involve Pull requests.

How do I install GitHub Issue Solve in Claude Code?

Run `npx skills add holon-run/holon --skill github-issue-solve -a claude-code`. Or copy the skill folder (skills/github-issue-solve in holon-run/holon) into .claude/skills/github-issue-solve in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Solve in Codex?

Run `npx skills add holon-run/holon --skill github-issue-solve -a codex`. Or copy the skill folder (skills/github-issue-solve in holon-run/holon) into .agents/skills/github-issue-solve in your project. Codex loads it when a task matches its description.

Can I use GitHub Issue Solve in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add holon-run/holon --skill github-issue-solve -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issue-solve, .gemini/skills/github-issue-solve, .github/skills/github-issue-solve and .opencode/skills/github-issue-solve in your project.

What does GitHub Issue Solve need to run?

Going by SKILL.md and its folder, GitHub Issue Solve needs the command-line tools its instructions call (gh) and credentials named GITHUB_TOKEN and GH_TOKEN. Our summary lists: A credential in GITHUB_TOKEN.

Does GitHub Issue Solve access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Issue Solve safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Issue Solve use?

GitHub Issue Solve is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issue Solve use?

About 912 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 494 tokens, read only when the agent opens those files.

What are the alternatives to GitHub Issue Solve?

Skills that share tags, products or a category with GitHub Issue Solve: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Solve?

holon-run (a GitHub organization) maintains it in holon-run/holon, which has 152 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

Source: holon-run/holon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.