Agent Skills › Tracer-Cloud/opensre › github-ci-fix

github-ci-fix

GitHub

用于修复 GitHub PR 中失败的 CI 检查。该技能自动分析失败原因，在本地分支执行修复、提交并推送，随后验证 CI 状态，确保 PR 恢复通过。

integrations/github/tools/ci_fix/SKILL.md Tracer-Cloud/opensre

Trigger Scenarios

GitHub PR CI 检查失败修复断开的 PR 分支

Install

npx skills add Tracer-Cloud/opensre --skill github-ci-fix -g -y

More Options

Non-standard path

npx skills add https://github.com/Tracer-Cloud/opensre/tree/main/integrations/github/tools/ci_fix -g -y

Use without installing

npx skills use Tracer-Cloud/opensre@github-ci-fix

指定 Agent (Claude Code)

npx skills add Tracer-Cloud/opensre --skill github-ci-fix -a claude-code -g -y

安装 repo 全部 skill

npx skills add Tracer-Cloud/opensre --all -g -y

预览 repo 内 skill

npx skills add Tracer-Cloud/opensre --list

SKILL.md

Frontmatter

{
    "name": "github-ci-fix",
    "tools": [
        "fix_github_pr_ci"
    ],
    "description": "Use when the user asks OpenSRE to fix failing GitHub PR CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or to fix CI and push back to the branch."
}

GitHub PR CI Fix

Use fix_github_pr_ci for GitHub pull request CI remediation requests, not github_cli or shell_run.

Rules:

Pass pr_url when the user provides a GitHub pull request URL.
Pass owner, repo, and pr_number when the user names a repo and PR number.
If no repo is named, omit owner and repo; the tool uses the current checkout's GitHub origin.
The tool inspects failing GitHub Actions checks, fixes the local checkout, commits, pushes to the PR's existing head branch, and waits for the checks triggered by that push. It does not open a new PR.
Fork PR branches are refused by the tool because OpenSRE only pushes to branches in the same repository.
The tool owns CI log inspection, fix execution, branch checkout, commit, and push plus post-push check verification. Do not run a raw gh workflow around it.
If the tool returns response_text, output exactly that text and stop.
If no fix is produced, keep the reply to one short line from error; do not say "next steps", add numbered options, list example commands, or ask a broad follow-up question.