Agent skill

GitHub PR Fix

by holon-run in holon-run/holon

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

Apache-2.0Auto-check passedTesting & QA

Install GitHub PR Fix

skills CLI
$ npx skills add holon-run/holon --skill github-pr-fix -a claude-code

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

GitHub CLI
$ gh skill install holon-run/holon github-pr-fix --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-pr-fix .claude/skills/github-pr-fix && 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-pr-fix
GitHub stars
153
Token cost
~1k tokens
SKILL.md length
397 words
Files
3 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 5 steps: Collect context → Diagnose and prioritize → Implement fixes → …
  • Tasks that involve Failing and flaky tests
  • 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 PR Fix is an agent skill from holon-run/holon. Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/diagnostics.md` and `references/pr-fix-workflow.md`).

It sits in Testing & QA, covering Failing and flaky tests. 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 Failing and flaky tests

Example prompts

  • “/github-pr-fix”

Requirements

  • A credential in GITHUB_TOKEN

Workflow steps

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

  1. Collect context
  2. Diagnose and prioritize
  3. Implement fixes
  4. Publish review replies
  5. Finalize delivery

What it can do on your machine

Read from SKILL.md and the folder at commit 671bd7a. 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 PR Fix loads about 1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 30 tokens; SKILL.md has 397 words of instructions outside code blocks.

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

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 671bd7a, republished under its Apache-2.0 licence (© holon-run). 397 words, ~1,033 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr-fix/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
github-pr-fix
description
Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies.

GitHub PR Fix Skill

Summary

Use this skill when you need to remediate an existing pull request: diagnose what is broken, apply targeted fixes, push commits, and reply on review threads.

When To Use

  • Fixing CI failures on an existing PR
  • Addressing requested changes or review feedback
  • Updating the PR branch and publishing review replies

Do Not Use

  • Opening a brand-new PR from an issue
  • Performing a review-only pass without code changes
  • Project-wide triage or roadmap planning

Prerequisites

  • gh CLI authentication is required.
  • GITHUB_TOKEN/GH_TOKEN must allow 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 PR context directly with gh:

bash
gh pr view <pr_number> --repo <owner/repo> --json number,title,body,state,url,baseRefName,headRefName,headRefOid,author,createdAt,updatedAt,mergeable,reviews,changedFiles,additions,deletions
gh pr view <pr_number> --repo <owner/repo> --json files
gh api repos/<owner>/<repo>/issues/<pr_number>/comments --paginate
gh api graphql -f query='
  query($owner:String!, $repo:String!, $number:Int!) {
    repository(owner:$owner, name:$repo) {
      pullRequest(number:$number) {
        reviewThreads(first:100) {
          nodes {
            isResolved
            comments(first:100) {
              nodes { id body path line author { login } }
            }
          }
        }
      }
    }
  }' -F owner=<owner> -F repo=<repo> -F number=<pr_number>

Do not assume fixed github/*.json files. Resolve available context through artifact metadata (id, path, status, description).

Workflow

1. Collect context
  • If ${GITHUB_CONTEXT_DIR}/manifest.json exists, use it.
  • Otherwise, collect PR metadata, files, comments, and review threads directly with gh.
2. Diagnose and prioritize

Prioritize in this order:

  1. Build/compile failures
  2. Failing tests and runtime regressions
  3. Type/import/module errors
  4. Lint/style issues
  5. Non-blocking refactor suggestions

Use existing review threads/comments to avoid duplicate or stale responses.

Show full SKILL.md (178 more words)Show less
3. Implement fixes
  • Apply minimal targeted fixes for blocking issues first.
  • 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.
  • Commit and push before posting review replies.
4. Publish review replies

Use direct gh api reply operations:

bash
gh api repos/<owner>/<repo>/pulls/<pr_number>/comments \
  -X POST \
  -F in_reply_to=<comment_id> \
  -f body='Thanks, fixed in the latest commit.'
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.

Remediation Standards

  • Do not mark issues fixed without verification evidence.
  • If verification is partial, state exact limits and risk.
  • Defer non-blocking large refactors with explicit rationale.
  • Keep review replies concrete: what changed, where, and any remaining risk.

Completion Criteria

A successful run requires all of the following:

  1. Blocking fixes are committed and pushed to the PR branch.
  2. Replies planned for this run are published successfully.
  3. The agent delivery records what changed, which replies were posted, and any remaining risks.

If replies are planned but not published, the run is not successful.

© 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 2 other files (references) in skills/github-pr-fix of holon-run/holon.

  • SKILL.md
  • references/diagnostics.md
  • references/pr-fix-workflow.md

Open the folder on GitHubat commit 671bd7a

Compare with similar skills

GitHub PR Fix 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 PR Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub PR Fix this skillholon-run/holon153—~1kAutomated safety check: PassApache-2.0
Triage CI Flakepayloadcms/payload45k—~4.4kAutomated safety check: PassMIT
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0
Fix Issueremix-run/remix33k—~1.8kAutomated safety check: PassMIT
Issue To Regression Testbrunosabot/streamline-card269—~529Automated safety check: PassMIT
Detect Flaky Testsagent-substrate/substrate4.5k—~3kAutomated safety check: PassApache-2.0

Similar skills

  • Triage CI Flake

    payloadcms/payload

    A skill your agent uses when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests

    45k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Fix Issue

    remix-run/remix

    Fix a reported issue in Remix from a GitHub issue. An agent skill from remix-run/remix.

    33k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Issue To Regression Test

    brunosabot/streamline-card

    A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.

    269 GitHub stars~529 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Detect Flaky Tests

    agent-substrate/substrate

    Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM…

    4.5k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Investigate and fix flaky/random CI test failures in dotnet/macios.

    2.9k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-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.

    153 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • GitHub Issue Solve

    holon-run/holon

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

    153 GitHub stars~912 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…

    153 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.

    153 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.

    153 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.

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

Works with

Categories

Questions about GitHub PR Fix

What does GitHub PR Fix do?

Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies. GitHub PR Fix is an agent skill from holon-run/holon. Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies.

When should I use GitHub PR Fix?

GitHub PR Fix fits situations like: tasks that involve Failing and flaky tests.

How do I install GitHub PR Fix in Claude Code?

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

How do I install GitHub PR Fix in Codex?

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

Can I use GitHub PR Fix 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-pr-fix -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-pr-fix, .gemini/skills/github-pr-fix, .github/skills/github-pr-fix and .opencode/skills/github-pr-fix in your project.

What does GitHub PR Fix need to run?

Going by SKILL.md and its folder, GitHub PR Fix 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 PR Fix 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 PR Fix 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 PR Fix use?

GitHub PR Fix 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 PR Fix use?

About 1k tokens (SKILL.md is roughly 4.1k 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 705 tokens, read only when the agent opens those files.

What are the alternatives to GitHub PR Fix?

Skills that share tags, products or a category with GitHub PR Fix: Triage CI Flake (payloadcms/payload, 45k stars), GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), Fix Issue (remix-run/remix, 33k stars) and Issue To Regression Test (brunosabot/streamline-card, 269 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub PR Fix?

holon-run (a GitHub organization) maintains it in holon-run/holon, which has 153 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 8, 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.