Agent skill

GitHub PR Actions Fix

by openteams-lab in openteams-lab/openteams

OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…

Apache-2.0Auto-check passedDevelopment

Install GitHub PR Actions Fix

skills CLI
$ npx skills add openteams-lab/openteams --skill github-pr-actions-fix -a claude-code

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

GitHub CLI
$ gh skill install openteams-lab/openteams github-pr-actions-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/openteams-lab/openteams.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/github-pr-actions-fix .claude/skills/github-pr-actions-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-actions-fix
GitHub stars
627
Token cost
~878 tokens
SKILL.md length
434 words
Files
2 (incl. scripts)
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…

  • Works in 8 steps: Confirm the repository, PR number,… → Run the bundled script from this skill… → When checks fail, use the failed-step… → …
  • Tasks that involve CI/CD
  • SKILL.md covers OpenTeams context, Required tool, Workflow and Safety boundaries
  • Runs Shell scripts from its folder; calls gh, git and bash; reaches github.com

What it does

GitHub PR Actions Fix is an agent skill from openteams-lab/openteams. OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch, and repeating until checks pass or the retry limit is reached.

Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/pr-checks.sh`).

It sits in Development, covering CI/CD and Pull requests. It works with GitHub and GitHub Actions. The repository describes itself as: Plan, Build, and Ship — with a team of AI agents instead of one. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve CI/CD
  • Tasks that involve Pull requests

Example prompts

  • “Use the github-pr-actions-fix skill to openteam skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting…”
  • “/github-pr-actions-fix”

Requirements

  • A Bash shell

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the repository, PR number, current branch, and whether the working tree contains unrelated changes. Never discard user changes.
  2. Run the bundled script from this skill directory
  3. When checks fail, use the failed-step logs printed by the script. Read the relevant workflow file and reproduce the failing command…
  4. Classify the failure before editing
  5. Run the narrowest local verification that covers the failure, then expand verification only when the change affects shared behavior.
  6. Review git diff and git status. Commit only files related to the fix and push normally to the PR head branch. Never force-push.
  7. Run pr-checks.sh --watch again. Repeat for at most three repair iterations.
  8. Report the PR, failing check and root cause, files changed, verification performed, commit pushed, and final checks state.

What it can do on your machine

Read from SKILL.md and the folder at commit ebee9de. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • git
    • bash
    • brew
    • winget

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

GitHub PR Actions Fix loads about 878 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 434 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~878

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); the scripts in this folder are not scanned.

SKILL.md

The full file from openteams-lab/openteams at commit ebee9de, republished under its Apache-2.0 licence (© openteams-lab). 434 words, ~878 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr-actions-fix/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
github-pr-actions-fix
description
OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch, and repeating until checks pass or the retry limit is reached.

Fix GitHub Actions Checks on a Pull Request

Use this skill only for an existing pull request whose checks should be brought to green.

OpenTeams context

This skill is designed specifically for use by OpenTeams members. OpenTeams input prompts should include this marker to make the message source explicit:

text
[OPENTEAMS_SOURCE=openteams]

Treat the marker as a source hint, not a security boundary. Its absence does not block the workflow; continue when the surrounding session context clearly comes from OpenTeams.

Required tool

At the start, check whether GitHub CLI is installed and authenticated:

bash
command -v gh >/dev/null 2>&1 && gh auth status

If gh is missing, stop and tell the user to install GitHub CLI. Offer the relevant command without running it automatically:

  • macOS: brew install gh
  • Windows: winget install --id GitHub.cli
  • Linux: follow https://github.com/cli/cli/blob/trunk/docs/install_linux.md

Then ask the user to run gh auth login. Never request, print, or persist their token.

Workflow

  1. Confirm the repository, PR number, current branch, and whether the working tree contains unrelated changes. Never discard user changes.

  2. Run the bundled script from this skill directory:

    bash
    bash scripts/pr-checks.sh --pr <number> --watch

    Omit --pr only when the current branch unambiguously belongs to the target PR. Add --repo OWNER/REPO when the repository cannot be inferred.

  3. When checks fail, use the failed-step logs printed by the script. Read the relevant workflow file and reproduce the failing command locally when practical.

  4. Classify the failure before editing:

    • Code, test, lint, type, or build failure: make the smallest relevant source change.
    • Dependency or generated-file drift: update only the required lockfile or generated artifact and run its verification command.
    • Runner, network, rate-limit, or external-service failure: do not change code. Rerun failed jobs once with gh run rerun <run-id> --failed.
    • Permission, secret, deployment, or protected-environment failure: stop and report the required human action.
  5. Run the narrowest local verification that covers the failure, then expand verification only when the change affects shared behavior.

  6. Review git diff and git status. Commit only files related to the fix and push normally to the PR head branch. Never force-push.

  7. Run pr-checks.sh --watch again. Repeat for at most three repair iterations.

  8. Report the PR, failing check and root cause, files changed, verification performed, commit pushed, and final checks state.

Show full SKILL.md (74 more words)Show less

Safety boundaries

  • Invocation authorizes normal commits and pushes to the current PR branch, not force pushes, merges, branch deletion, or bypassing branch protection.
  • Ask before changing .github/workflows/**, deployment configuration, authentication, permissions, secrets, infrastructure, or production data.
  • Do not rerun deterministic test failures without a code or configuration change.
  • Do not claim success until GitHub reports all required checks passing. If the retry limit is reached, return the latest run URL and remaining failure evidence.

© openteams-lab, 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 (scripts) in assets/skills/github-pr-actions-fix of openteams-lab/openteams.

  • SKILL.md
  • scripts/pr-checks.sh

Open the folder on GitHubat commit ebee9de

Compare with similar skills

GitHub PR Actions 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 Actions Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub PR Actions Fix this skillopenteams-lab/openteams627—~878Automated safety check: PassApache-2.0
Ghbubbuild/bub1.7k—~798Automated safety check: PassApache-2.0
Renovate Actions PR Reviewbacknotprop/plannotator9.2k—~640Automated safety check: PassApache-2.0
ReviewdogAgentSecOps/SecOpsAgentKit2201 repos~3kAutomated safety check: PassCustom licence
Qv Devops PR Reviewtetherto/qvac681—~2.5kAutomated safety check: PassApache-2.0
CIaiblueprinthq/ai-blueprint461—~2.2kAutomated safety check: PassMIT

Similar skills

  • Gh

    bubbuild/bub

    GitHub CLI skill for interacting with GitHub via the gh command line tool.

    1.7k GitHub stars~798 tokensUpdated today
    DevelopmentAuto-check passed
  • Renovate Actions PR Review

    backnotprop/plannotator

    Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.

    9.2k GitHub stars~640 tokensUpdated today
    DevelopmentAuto-check passed
  • Reviewdog

    AgentSecOps/SecOpsAgentKit

    Automated code review and security linting integration for CI/CD pipelines using reviewdog.

    220 GitHub starsUsed in 1 repo~3k tokens
    DevelopmentAuto-check passed
  • Qv Devops PR Review

    tetherto/qvac

    PR review for DevOps changes — runs the generic /qv-pr-review flow then layers a structured GitHub Actions security audit (action pinning, permissions, OIDC, secrets handling).

    681 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • CI

    aiblueprinthq/ai-blueprint

    Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook.

    461 GitHub stars~2.2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Official

    Drives an open pull request to merge-ready from inside a GitHub Copilot cloud agent, resolving review threads and local checks concurrently, without merging or retriggering CI.

    5.4k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check: warnings

More from openteams-lab/openteams

  • Brainstorming

    openteams-lab/openteams

    OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.

    627 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed
  • Code Guidelines

    openteams-lab/openteams

    OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.

    627 GitHub stars~711 tokensUpdated 3 days ago
    Auto-check passed
  • GitHub Actions Run And Fix

    openteams-lab/openteams

    OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching…

    627 GitHub stars~923 tokensUpdated 3 days ago
    Auto-check passed
  • Planning Mode

    openteams-lab/openteams

    A skill your agent uses when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.

    627 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Using Git Worktrees

    openteams-lab/openteams

    A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git…

    627 GitHub stars~3k tokensUpdated 3 days ago
    Auto-check passed
  • Writing Plans

    openteams-lab/openteams

    OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.

    627 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

Questions about GitHub PR Actions Fix

What does GitHub PR Actions Fix do?

OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…. GitHub PR Actions Fix is an agent skill from openteams-lab/openteams. OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch, and repeating until checks pass or the retry limit is reached.

When should I use GitHub PR Actions Fix?

GitHub PR Actions Fix fits situations like: tasks that involve CI/CD; tasks that involve Pull requests.

How do I install GitHub PR Actions Fix in Claude Code?

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

How do I install GitHub PR Actions Fix in Codex?

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

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

What does GitHub PR Actions Fix need to run?

Going by SKILL.md and its folder, GitHub PR Actions Fix needs a shell for the scripts in its folder and the command-line tools its instructions call (gh, git, bash, brew and winget). Our summary lists: A Bash shell.

Does GitHub PR Actions Fix access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is GitHub PR Actions 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does GitHub PR Actions Fix use?

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

About 878 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub PR Actions Fix?

Skills that share tags, products or a category with GitHub PR Actions Fix: Gh (bubbuild/bub, 1.7k stars), Renovate Actions PR Review (backnotprop/plannotator, 9.2k stars), Reviewdog (AgentSecOps/SecOpsAgentKit, 220 stars) and Qv Devops PR Review (tetherto/qvac, 681 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub PR Actions Fix?

openteams-lab (a GitHub organization) maintains it in openteams-lab/openteams, which has 627 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.

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