Agent Skills › warpdotdev/oz-skills › ci-fix

ci-fix

GitHub

诊断并修复 GitHub Actions CI 失败。通过分析工作流日志定位根因，实施最小化修复并推送到专用分支，无需创建 PR，适用于 CI 构建或测试失败场景。

.agents/skills/ci-fix/SKILL.md warpdotdev/oz-skills

Trigger Scenarios

CI 流程失败 GitHub Actions 检查报错需要自动修复流水线问题

Install

npx skills add warpdotdev/oz-skills --skill ci-fix -g -y

More Options

Non-standard path

npx skills add https://github.com/warpdotdev/oz-skills/tree/main/.agents/skills/ci-fix -g -y

Use without installing

npx skills use warpdotdev/oz-skills@ci-fix

指定 Agent (Claude Code)

npx skills add warpdotdev/oz-skills --skill ci-fix -a claude-code -g -y

安装 repo 全部 skill

npx skills add warpdotdev/oz-skills --all -g -y

预览 repo 内 skill

npx skills add warpdotdev/oz-skills --list

SKILL.md

Frontmatter

{
    "name": "ci-fix",
    "license": "MIT",
    "description": "Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis."
}

CI Fix

Diagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs.

Prerequisites

Verify GitHub CLI authentication before proceeding:

gh auth status

If not authenticated, instruct the user to run gh auth login first.

Workflow

1. Locate the Failing Run

Determine the failing workflow run. If working on a PR branch:

gh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == "FAILURE")'

If working from a branch or run ID:

gh run list --branch <branch> --status failure --limit 5
gh run view <run-id> --verbose

2. Extract Failure Logs

Pull logs from failed steps to identify the root cause:

gh run view <run-id> --log-failed

For deeper inspection:

gh run view <run-id> --log --job <job-id>
gh run download <run-id> -D .artifacts/<run-id>

3. Identify Root Cause

Analyze logs for common failure patterns:

Build/compilation errors: Missing dependencies, type errors, syntax issues
Test failures: Assertion failures, timeouts, flaky tests
Linting/formatting: Style violations, unused imports
Environment issues: Missing secrets, permissions, resource limits

Prefer the smallest fix that resolves the issue. Deterministic code fixes are better than workflow plumbing changes.

4. Implement the Fix

Make minimal, scoped changes matching the repository's existing style:

Fix only what's broken—avoid unrelated refactoring
Keep changes to the failing job/step when possible
If modifying workflow files, preserve existing permissions and avoid expanding token access

5. Push to Fix Branch

Create or update a dedicated fix branch:

git checkout -b ci-fix/<original-branch>
git add -A
git commit -m "fix: resolve CI failure in <job-name>

Co-Authored-By: Warp <agent@warp.dev>"
git push -u origin ci-fix/<original-branch>

If the fix branch already exists, update it:

git checkout ci-fix/<original-branch>
git pull origin <original-branch>
# make fixes
git commit -m "fix: <description>

Co-Authored-By: Warp <agent@warp.dev>"
git push

6. Verify the Fix

Trigger CI on the fix branch and monitor:

gh run list --branch ci-fix/<original-branch> --limit 1
gh run watch <new-run-id> --exit-status

To rerun only failed jobs:

gh run rerun <run-id> --failed

Safety Notes

Avoid pull_request_target unless explicitly requested—it can expose secrets to untrusted code
Keep workflow permissions: minimal; don't broaden access to make tests pass
For flaky tests, prefer deterministic fixes over blind reruns